Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search TikTok Top results

tiktok_search_top_list
Read-onlyIdempotent

Search TikTok Top results by keyword to find mixed content beyond videos. Use it for keyword research and trend discovery, with filters for region, date, and sort order.

Instructions

Search TikTok Top results by keyword (not videos-only — use tiktok_search_videos_list for that). Requires query. Returns a list (use cursor when paginated).

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_top_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Search query text for TikTok Top results.
cursorNoOpaque pagination cursor returned by a previous response.
regionNoOptional two-letter ISO 3166-1 country code for localized search results.
sortByNoOptional sort order for search results.
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.
datePostedNoOptional upload date filter for video results.
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the safety profile needs no restating. The description adds real behavior beyond that: results come back as a list and pagination is cursor-based, which tells the agent to loop on the cursor rather than assume a single page.

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?

Two compact sentences, front-loaded with the primary action, then the sibling exclusion, then the return/pagination note. Nothing is padded or redundant.

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?

With 8 parameters, 3 required, and no output schema, the description should say more about what a 'Top result' item actually contains. It only says 'Returns a list', leaving the result shape to inference, though the fully documented input schema and annotations cover the calling side.

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 every parameter including `cursor`, `region`, `sortBy`, `datePosted` and `conversation_id` is already documented in the schema. The description only repeats that `query` is required and that `cursor` is for pagination, adding no syntax or constraint detail beyond the structured fields.

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?

States a specific verb (Search) and resource (TikTok Top results) by keyword, and explicitly contrasts itself with the videos-only sibling `tiktok_search_videos_list`, so an agent can pick between them without opening either schema.

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?

Gives a clear selection rule: use this for general Top results, use `tiktok_search_videos_list` when you want videos only. That is an explicit when/when-not pair with a named alternative, though it is the only routing guidance given.

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