Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search TikTok users

tiktok_users_search
Read-onlyIdempotent

Search TikTok users by keyword to find real handles before fetching profiles, helping you avoid inventing usernames.

Instructions

Search TikTok users by keyword. Requires query. Discover real handles before profile gets; avoid inventing usernames.

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

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Search query text for TikTok users.
cursorNoOpaque pagination cursor returned by a previous response.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without the description. The description adds the discovery-oriented behavior (returns real handles), but says nothing about result volume, ranking, or pagination via the cursor parameter.

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?

Two short sentences, front-loaded with the resource and keyword semantics, with no filler. The phrase 'before profile gets' is slightly compressed jargon but still readable.

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?

For a read-only open-world search with fully documented parameters and no output schema, the definition covers purpose, the required input, and the anti-hallucination intent. Only the shape of results and pagination behavior are left implicit.

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% across all five parameters, including the detailed context, llm_model, and conversation_id descriptions, so the schema carries the burden. The description only calls out that `query` is required, which repeats what the schema already marks as required. 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 states a specific verb and resource ('Search TikTok users by keyword'), which distinguishes it from list/get-style siblings such as tiktok_users_get-style profile fetches and the tiktok_search_* family. It stops short of naming any alternative explicitly, so it is clear but not fully sibling-differentiated.

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?

It gives concrete usage guidance: use this to discover real handles before fetching profiles, and do not invent usernames. What's missing is a when-not clause or a named alternative for cases where a direct profile lookup is already known.

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