Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok search suggestions

tiktok_search_suggestions_list
Read-onlyIdempotent

Fetches a list of TikTok search suggestions for a query, helping you discover related keywords and region-specific terms for content research.

Instructions

Get TikTok search suggestions by query. Requires query. Returns a list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_search_suggestions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Search query text for TikTok suggestions.
regionNoOptional two-letter ISO 3166-1 country code for localized suggestions.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds almost nothing on top of that: 'Returns a list' is essentially tautological given the tool name ends in _list, and the more consequential behavior — the conversation_id handshake and the analytics use of llm_model — is described only in the schema, not here.

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?

Three short sentences, front-loaded with the verb and resource, with no filler or marketing language. However, two of the three sentences ('Requires `query`' and 'Returns a list') duplicate structured data the agent already has, so a small amount of the text does not earn its place.

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 simple read-only list retrieval with full schema coverage and four meaningful annotations, the description is adequate but thin. It omits the multi-call conversation flow implied by the required conversation_id and context parameters, which is the one piece of non-obvious behavior an agent would benefit from seeing up front.

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%, including the orchestration parameters context, llm_model and conversation_id, so the schema carries the full burden of parameter meaning. The description merely restates that query is required, which the schema already marks as required with a description, so the baseline 3 applies.

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 uses a specific verb and resource ('Get TikTok search suggestions') and names the selector input ('by query'), which is enough to distinguish it from the broader tiktok_search_top_list, tiktok_search_videos_list and tiktok_search_hashtag_list siblings that return results rather than suggestions. It stops short of explicitly contrasting itself with those siblings, so it lands just below the top band.

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?

There is an implied usage: the tool is for autocomplete/query-suggestion lookup before or alongside a real search. Beyond that, the description says nothing about when to prefer it over tiktok_search_top_list or tiktok_search_videos_list, and gives no exclusions or prerequisites, leaving the agent to infer the choice from the name alone.

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

Deploy Server

Other Tools