Skip to main content
Glama

Captapi

by io.github.CDCStream
OverviewDiscussionsAdmin

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).

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.
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 / 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."
  2. 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."
  3. 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."
  4. 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"
+}
  5. 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."
  6. 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"
+}
  7. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does add real value: billing is '2 credits', empty results and failures are 'never charged', and caching semantics are disclosed ('free 24h cache hit', default always fresh). It does not mention authentication or rate limits, but the billing and cache behavior is exactly the kind of context structured fields don't provide.

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?

The resource and vetting purpose are front-loaded, and billing/caching are packed into compact sentences. The jargon ('hydrate', 'ttSeller', 'bioLinkRisk') is dense and slightly opaque, but there is little outright filler.

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 7 optional parameters, no annotations, and no output schema, the description covers the essentials an agent needs: cost, no-charge conditions, caching, and the enrichment fields returned. It stops short of describing the response shape or ordering, but is largely sufficient for invocation.

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 description coverage is 100%, so the schema already documents all 7 parameters, setting the baseline at 3. The description only reinforces cache behavior ('default always fresh'), adding little semantic meaning beyond what the schema already states.

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 resource and source ('Creative Center creators') and an enrichment layer ('createTime / bioLinkRisk / ttSeller hydrate') aimed at 'partnership vetting'. An agent can tell it retrieves a ranked list of TikTok creators rather than, say, individual users. However, it lacks a clear verb and never differentiates itself from siblings like tiktok_search_users or tiktok_trending_feed, so the purpose is clear but not sibling-distinguished.

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?

'For partnership vetting' implies the intended scenario, and the credit/caching notes sketch operational context. But there is no explicit when-to-use vs. when-not, and no routing to alternatives such as tiktok_search_users, so usage is only implied.

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

All Captapi toolsInspect
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