UGC Chart

Search creators

search_creators

Read-onlyIdempotent

Find Trybe creators on UGC Chart. Filter by category, country, 30-day sales range, growth, approval rate and badges. Returns up to 50 creators per page with sales range (last 30 days), weeks growing in a row, videos sent in 30 days and approval rate (percent of their videos brands approved).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_creators"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order. growing = growing fastest first (default); top_sales = highest sales range; most_videos = most videos in 30 days; approval = highest approval rate; weeks_growing = most weeks in a row growing; chart_rank = Top 50 order.
`limit`	No	How many, 1 to 50. Default 20.
`niche`	No	Category, like "Skincare" or "Pets". See list_categories. Matches categories the creator picked on Trybe or ranks in; creators on Trybe's sales list for that category come first.
`badges`	No	Must have all of these badges. steady = 2+ weeks in a row in the same sales range; breakout = a confirmed jump in sales; few_videos_big_sales = high sales from few videos.
`offset`	No	Skip this many (for the next page).
`country`	No	2-letter country code, like "US".
`min_band`	No	Lowest 30-day sales range, like "50k+".
`growing_only`	No	Only creators whose sales are growing this week.
`min_approval`	No	Lowest approval rate, 0 to 100: the percent of this creator's videos that brands approved.
`min_weeks_growing`	No	Lowest number of weeks in a row growing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / badges / description

Previous value: -"Must have all of these badges. steady = 4+ weeks in the same sales range; breakout = a confirmed jump in sales; few_videos_big_sales = high sales from few videos."New value: +"Must have all of these badges. steady = 2+ weeks in a row in the same sales range; breakout = a confirmed jump in sales; few_videos_big_sales = high sales from few videos."

First observedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real behavioral context those annotations cannot: a hard cap of 50 creators per page and the shape of the returned record (sales range, weeks growing, videos sent, approval rate), which matters since there is no output schema.

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?

Two sentences, front-loaded with purpose before the return shape, and every clause carries information. The only waste is the redundant "(last 30 days)" sales-range phrasing repeated across both sentences.

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

Completeness4/5

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

With 10 optional parameters, no output schema and a full-coverage input schema, the description does the right extra work by explaining page size and returned fields. It stops short of mentioning pagination limits via offset (max 5000), total result counts, or default sort behavior, which are covered only in the schema.

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 the schema already carries full parameter documentation, and the description largely restates the same filter categories. It does add a plain-language gloss on what the returned metrics mean (approval rate as percent of videos brands approved, weeks growing in a row), but nothing about parameter syntax or interaction beyond the schema.

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

Purpose4/5

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

The description opens with a specific verb and resource ("Find Trybe creators on UGC Chart") and enumerates the filterable dimensions, so an agent immediately knows this is a filtered creator search. It does not explicitly contrast itself with siblings like get_creator or similar_creators, leaving the search-vs-lookup distinction implicit.

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

Usage Guidelines3/5

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

Usage is implied by the filter list rather than stated: an agent can infer this is the tool for browsing creators matching criteria. It gives one useful routing pointer ("See list_categories" for the niche parameter), but there is no guidance on when to prefer similar_creators, compare_creators, or get_creator instead.

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

All UGC Chart 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?