Skip to main content
Glama

captapi

by io.github.CDCStream
OverviewDiscussionsAdmin

tiktok_search_suggestions

Get the autocomplete terms TikTok suggests in its search bar for a keyword — the real phrases people search, ranked, so you can find trending queries and long-tail keyword ideas. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSeed keyword to expand into autocomplete suggestions, e.g. skincare.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax items to return (default 20, max 100). Flat 2 credits per call.
countryNoTwo-letter ISO country code that localizes the suggestions to a market, e.g. US, GB, DE. Default US.
languageNoInterface language for the suggestions, e.g. en-US or de-DE. Default en-US.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  2. Changed4 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 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter ISO country code that localizes suggestions to a market, e.g. US, GB, DE. Default US."New value: +"Two-letter ISO country code that localizes the suggestions to a market, e.g. US, GB, DE. Default US."
    • changedInput schema / properties / language / description
      Previous value: -"Interface language for localized results, e.g. en-US or de-DE. Default en-US."New value: +"Interface language for the suggestions, e.g. en-US or de-DE. Default en-US."
    • changedInput schema / properties / limit / description
      Previous value: -"Upper bound on suggestions to return (1-100, default 20). TikTok surfaces only a limited number of real autocomplete suggestions per keyword, so you'll often get fewer. Billed per result."New value: +"Max items to return (default 20, max 100). Flat 2 credits per call."
  3. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Flat 2 credits per call."New value: +"Upper bound on suggestions to return (1-100, default 20). TikTok surfaces only a limited number of real autocomplete suggestions per keyword, so you'll often get fewer. Billed per result."
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Upper bound on suggestions to return (1-100, default 20). TikTok surfaces only a limited number of real autocomplete suggestions per keyword, so you'll often get fewer. Billed per result."New value: +"Max items to return. Flat 2 credits per call."
  5. Changed1 schema field changed
    • changedInput schema / properties / language / description
      Previous value: -"Preferred caption language as an ISO code, e.g. \"en\". Defaults to auto-detect."New value: +"Interface language for localized results, e.g. en-US or de-DE. Default en-US."
  6. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 100. Billed per result."New value: +"Upper bound on suggestions to return (1-100, default 20). TikTok surfaces only a limited number of real autocomplete suggestions per keyword, so you'll often get fewer. Billed per result."
  7. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter ISO country code. Default US."New value: +"Two-letter ISO country code that localizes suggestions to a market, e.g. US, GB, DE. Default US."
    • changedInput schema / properties / q / description
      Previous value: -"Seed keyword for autocomplete suggestions."New value: +"Seed keyword to expand into autocomplete suggestions, e.g. skincare."
  8. 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."
  9. 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"
+}
  10. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a good job: it discloses a 2-credit cost, no charge for empty/failed results, and the 24h cache option with default always-fresh behavior. It does not mention potential rate limits or auth requirements, but the operational behavior most relevant to invoking correctly is covered.

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

Conciseness5/5

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

The description is compact, front-loaded with what the tool does, and every sentence earns its place: value proposition, cost, no-charge guarantee, and cache behavior. No redundant fluff or repetition of raw schema attributes.

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

Completeness5/5

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

For a 5-parameter tool with no output schema and no annotations, the description covers the essential context: what is returned, why it is useful, cost behavior, failure charging, and cache semantics. The remaining parameters are fully documented in the schema, so nothing an agent needs to select and invoke this tool correctly is missing.

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

Parameters4/5

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

The input schema already describes all five parameters (100% coverage), and the description adds meaningful semantics beyond the schema: 'q' is a seed keyword, cache=true yields a free 24h cache hit, and calls carry a flat 2-credit cost. Country and language are left to the schema, but the description raises the overall value.

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?

The description uses a specific verb ('Get the autocomplete terms TikTok suggests in its search bar for a keyword') and clearly identifies the resource and output. It distinguishes this tool from search-focused siblings by emphasizing autocomplete/ranked phrases for canonical and long-tail keyword discovery, not user/hashtag/top-search lists.

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?

The description clearly states the intended use case: finding trending queries and long-tail keyword ideas. It does not explicitly compare against alternatives or state when not to use it, but the context is clear enough that an agent can infer when this tool is appropriate.

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