Skip to main content
Glama

tiktok_popular_creators

Creative Center creators + createTime / bioLinkRisk / ttSeller hydrate for partnership vetting. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

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": "tiktok_popular_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoCreative Center page (default 1).
sortNofollower, engagement, or popularity. Default follower.
cacheNoSet true to serve from the response cache (default TTL). Default false — always fetch fresh. Prefer cacheMaxAge when you need 1d–30d freshness control.
limitNoMax items to return (default 20, max 100). Flat 2 credits per call.
fieldsNoOptional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.
compactNoDefault true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body.
countryNoTwo-letter ISO country code. Default US.
cacheMaxAgeNoMax age of a cached response: 1d, 3d, 7d, 14d, or 30d. When set, enables caching with that TTL.
follower_countNoOptional range on the For You ranking: 10k-100k, 100k-1m, 1m-10m, >10m.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body."New value: +"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body."
  2. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": true,
      +  "description": "Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / follower_count / description
      Previous value: -"Optional range on the For You / fallback path: 10k-100k, 100k-1m, 1m-10m, >10m."New value: +"Optional range on the For You ranking: 10k-100k, 100k-1m, 1m-10m, >10m."
  4. Changed1 schema field changed
    • changedInput schema / properties / follower_count / description
      Previous value: -"Optional range on FYP/Apify fallthrough: 10k-100k, 100k-1m, 1m-10m, >10m."New value: +"Optional range on the For You / fallback path: 10k-100k, 100k-1m, 1m-10m, >10m."
  5. Changed2 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the response cache (default TTL). Default false — always fetch fresh. Prefer cacheMaxAge when you need 1d–30d freshness control. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the response cache (default TTL). Default false — always fetch fresh. Prefer cacheMaxAge when you need 1d–30d freshness control."
    • changedInput schema / properties / cacheMaxAge / description
      Previous value: -"Max age of a cached response: 1d, 3d, 7d, 14d, or 30d. When set, enables caching with that TTL. Envelope: cached + cachedAt."New value: +"Max age of a cached response: 1d, 3d, 7d, 14d, or 30d. When set, enables caching with that TTL."
  6. Changed5 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the response cache (default TTL). Default false — always fetch fresh. Prefer cacheMaxAge when you need 1d–30d freshness control. Envelope includes cached + cachedAt on hits."
    • addedInput schema / properties / cacheMaxAge
      Added value: +{
      +  "description": "Max age of a cached response: 1d, 3d, 7d, 14d, or 30d. When set, enables caching with that TTL. Envelope: cached + cachedAt.",
      +  "type": "string"
      +}
    • changedInput schema / properties / follower_count / description
      Previous value: -"Optional range: 10k-100k, 100k-1m, 1m-10m, >10m."New value: +"Optional range on FYP/Apify fallthrough: 10k-100k, 100k-1m, 1m-10m, >10m."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 100. Billed per result."New value: +"Max items to return (default 20, max 100). Flat 2 credits per call."
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Creative Center page (default 1).",
      +  "minimum": 1,
      +  "type": "integer"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  8. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
      +  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
      +  "type": "boolean"
      +}
  9. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses the 2-credit cost, that empty results and failures are never charged, and the 24h free cache behavior versus always-fresh default. It does not describe the shape of the hydrated creator records, but the pricing and failure semantics are substantial.

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?

Purpose is front-loaded in the first clause, followed by cost and cache notes in a compact two-sentence body with no filler. The dense slash-delimited hydrate list is slightly opaque but earns its space.

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 9-parameter, no-annotation, no-output-schema tool, the description covers cost and caching well but says nothing about result ordering, pagination behavior, or what the hydrated fields actually contain. Adequate but with clear gaps.

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 baseline is 3. The description only echoes the cache=true free-hit behavior already documented in the cache parameter; it adds no meaning for page, sort, country, limit, fields, or follower_count 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 names a specific source (Creative Center creators) and adds the hydrate fields (createTime, bioLinkRisk, ttSeller) plus the intent, partnership vetting. It is clearly distinct from sibling list tools like tiktok_popular_hashtags, though the slash-separated jargon requires some interpretation.

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?

The 'for partnership vetting' phrase implies the use case, and the caching guidance implies when to prefer cache. But there is no explicit when-to-use vs. when-not guidance and no named alternative among the siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.