Skip to main content
Glama

tiktok_search_user

Read-only

Searches TikTok users by keyword with cursor-based pagination. Use tiktok_search to search TikTok videos.

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": {
      "keyword": "<keyword>"
    },
    "name": "tiktok_search_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor; pass the cursor from a previous response. Default 0.
keywordYesTikTok user search keyword (required). Example: chatgpt.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds that results are paginated via a cursor — a behavioral trait annotations do not cover. It does not mention rate limits or auth, but with the safety profile already declared, this is solid added context.

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 tightly-worded sentences: the scope/mechanism first, the sibling disambiguation second. Zero filler and correctly front-loaded.

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?

An output schema exists, so return values need no explanation, and the description covers the input contract and the key sibling boundary. It is complete for practical invocation, though it says nothing about how the cursor terminates or result volume.

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 both 'keyword' and 'cursor' are fully documented in the schema, including that the cursor comes from a previous response. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 and resource ('Searches TikTok users by keyword') and explicitly contrasts with the sibling tiktok_search, which handles videos. An agent can route between the two 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?

Provides explicit negative routing ('Use tiktok_search to search TikTok videos'), which tells the agent when this tool is the wrong choice. It doesn't address other plausible siblings like tiktok_profile or tiktok_search_hashtag, but the core user-vs-video distinction is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.