Creator River

Find creators by description and filters

search_creators

Read-only

Searches the creator database by meaning: describe the creators you want in plain words (niche, content, audience), and optionally narrow by platform, niche, creator country, audience country, language, size, engagement rate and how recently they posted. To find creators like ones the user already knows, pass their handles or profile links as exampleCreators. Free, but each call counts against the daily search limit (see get_account). Results show each creator’s name but no handle or profile link. Pass campaignId to rank against that campaign’s brief and record the search in it.

Input Schema

Name	Required	Description
`limit`	No	How many to return, 1-100 (default 20)
`query`	Yes	The creators you want, in plain words: niche, what their content is like, who watches it
`niches`	No	Only creators whose main content is one of these niches. Creators who cover many topics are filed under none, so leave this out for broad lifestyle searches
`markets`	No	Only creators based in these countries: two-letter codes, e.g. us, gb, jp
`languages`	No	Only creators posting in these languages: two-letter codes, e.g. en, es, ja
`platforms`	No	Only creators on these platforms
`campaignId`	No	Rank for this campaign and record the search in it
`maxAvgViews`	No	At most this many average views per post
`minAvgViews`	No	At least this many average views per post
`maxFollowers`	No	At most this many followers
`minFollowers`	No	At least this many followers
`exampleCreators`	No	Creators to find more like: @handles or profile links, e.g. @mkbhd or https://www.tiktok.com/@khaby.lame. The query still says what they should share. Ones not found are listed in warnings
`audienceCountries`	No	Only creators whose largest audience is in these countries: two-letter codes, e.g. us, gb, th
`maxEngagementRate`	No	At most this engagement rate, as a fraction: 0.1 for 10%
`minEngagementRate`	No	At least this engagement rate, as a fraction: 0.02 for 2%
`lastPostWithinDays`	No	Only creators whose latest post is at most this many days old: 7, 14, 30, 90 or 180

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 4, 2026

changedInput schema / properties / audienceCountries / description

Previous value: -"Only creators whose largest audience is in these countries, e.g. us, gb, th"New value: +"Only creators whose largest audience is in these countries: two-letter codes, e.g. us, gb, th"

addedInput schema / properties / exampleCreators

Added value: +{
+  "description": "Creators to find more like: @handles or profile links, e.g. @mkbhd or https://www.tiktok.com/@khaby.lame. The query still says what they should share. Ones not found are listed in warnings",
+  "items": {
+    "maxLength": 300,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

changedInput schema / properties / languages / description

Previous value: -"Only creators posting in these languages, e.g. english"New value: +"Only creators posting in these languages: two-letter codes, e.g. en, es, ja"

changedInput schema / properties / markets / description

Previous value: -"Only creators in these countries, e.g. us, gb, jp"New value: +"Only creators based in these countries: two-letter codes, e.g. us, gb, jp"

addedInput schema / properties / niches

Added value: +{
+  "description": "Only creators whose main content is one of these niches. Creators who cover many topics are filed under none, so leave this out for broad lifestyle searches",
+  "items": {
+    "enum": [
+      "music",
+      "gaming",
+      "tech",
+      "beauty",
+      "food",
+      "sports",
+      "fitness",
+      "travel",
+      "pets",
+      "fashion",
+      "health",
+      "education",
+      "comedy",
+      "cars",
+      "parenting"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / query / description

Previous value: -"The creators you want, in plain words"New value: +"The creators you want, in plain words: niche, what their content is like, who watches it"

First observedOct 29, 2026

TDQS

A4.2/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint/openWorldHint it discloses quota consumption, the key output limitation (names shown but no handle or profile link, implying another tool is needed for contact), that unfound example creators surface in warnings, and that campaignId causes the search to be ranked against and recorded in that campaign.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core search mechanic, then secondary behaviors (limits, output limitation, campaign recording) in descending order of importance. Slightly redundant phrasing ("describe the creators you want in plain words" repeats the query schema text) keeps it from a 5, but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter semantic search with no output schema, the description covers cost, one output limitation, and the campaign side effect, which is solid. It does not describe what a result record contains (followers, engagement, platform) or result ordering/limit behavior, so an agent still lacks a full picture of the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all 16 parameters are already documented, and the description mostly restates the facet list (platform, niche, country, language, size, engagement, recency) rather than adding syntax or edge-case meaning. It does add intent framing for exampleCreators and campaignId, but that intent is largely mirrored in the schema descriptions, so the baseline 3 fits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Searches the creator database by meaning") and immediately explains the input mode: describe creators in plain words, optionally narrowed by facets. It is clearly distinguishable from siblings like get_creator (single lookup) and from non-search tools such as list_campaigns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit conditions for the two interesting paths: use plain-word query for discovery and pass exampleCreators "to find creators like ones the user already knows." It also states the cost model (free but counts against the daily search limit) and points to get_account for the limit. It stops short of naming when to prefer get_creator or unlock_creator instead, so no full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Creator River tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?