# creator_lookup

> Find and size creators.

URL: https://mcp-docs.opennomos.com/docs/tools/research/creator_lookup

> Find and size creators. action=youtube_search (`query`, e.g. 'indie hacker') → channels with subscribers text; ~5s, $0.001. action=xiaohongshu_search (`query` in Chinese, e.g. '独立开发') → users with fans text; ~3s, $0.01. action=xiaohongshu_notes (`id` = user id from xiaohongshu_search) → their recent notes, returned directly; ~3s, $0.01. action=x_profile (`id` = handle without @) → followers, posts, bio, website; ~3s, $0.001. action=tiktok_creator (`id` = numeric TikTok user id) → followers, likes; ~3s, $0.001.>
> Searches and profiles return results; xiaohongshu_notes returns notes without storing memory.

| Field | Value |
| --- | --- |
| Pack | Creators (`creators`) |
| Estimated cost per call | ~$0.01 (upstream cost; see the description for per-action figures) |
| Monthly pack limit | $2 of upstream cost (not shown to users) |
| Project | optional (`project` or `X-OpenNomos-Project`); only attaches the project id to the result |

## Parameters

| Parameter | Required | Type | Description |
| --- | --- | --- | --- |
| `project` | no | `string` | Project slug or id. Omit to use the credential or workspace default. |
| `action` | yes | `"youtube_search"` \| `"xiaohongshu_search"` \| `"xiaohongshu_notes"` \| `"x_profile"` \| `"tiktok_creator"` | What to look up; each action uses `query` or `id` as described in the tool description. |
| `query` | no | `string` | youtube_search / xiaohongshu_search: search text, e.g. 'indie hacker' or '独立开发'. |
| `id` | no | `string` | xiaohongshu_notes: user id from xiaohongshu_search. x_profile: handle, e.g. 'levelsio' (@ optional). tiktok_creator: numeric TikTok user id. |

## Example call

```json
{
  "action": "xiaohongshu_search",
  "query": "独立开发"
}
```

REST: `POST https://service.opennomos.com/v1/tools/creator_lookup` with that JSON as the body. MCP: `tools/call` with `name: "creator_lookup"` and that JSON as `arguments`.

## Example result

Values are illustrative; the shape comes from the service code.

```json
{
  "results": [
    {
      "platform": "xiaohongshu",
      "id": "5f1a…",
      "name": "…",
      "red_id": "…",
      "followers": "1.2万粉丝",
      "description": "…",
      "verified": false,
      "url": "https://www.xiaohongshu.com/user/profile/5f1a…"
    }
  ]
}
```

## Notes

- Five actions: `youtube_search`, `xiaohongshu_search`, `xiaohongshu_notes`, `x_profile` and `tiktok_creator`. Which of `query` or `id` each uses is in the description above.
- `x_profile` returns followers, following, post count, bio and website for one handle. `xiaohongshu_notes` returns a creator's recent notes, with note links that include the `xsec_token` they need to open.
- Follower counts from search are text as the source shows them (for example `1.2万粉丝`), not numbers.

## Errors

Upstream trouble is reported **inside a normal result** as `error`, `reason` and `action` (and `tool` / `retry_after_seconds` when they apply). For `search_signals` this appears per source. See [Errors](https://mcp-docs.opennomos.com/docs/reference/errors.md).

This tool is in the **Creators** pack. If the pack is not enabled the call fails with `pack_required` (HTTP 403); if the pack's monthly upstream cost limit is used up it fails with `soft_limit` (HTTP 429). Both carry `action: "give_up_and_tell_user"` and the console URL.