Crawlora MCP

tiktok_search

Read-only

Searches TikTok videos by keyword with cursor-based pagination. count: Number of results, clamped to 50. Default 20. Use tiktok_search_user to search TikTok users.

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

Input Schema

Name	Required	Description
`count`	No	Number of results, clamped to 50. Default 20.
`cursor`	No	Pagination cursor; pass the cursor from a previous response. Default 0.
`keyword`	Yes	TikTok video search keyword (required). Example: dance.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds cursor-based pagination and the 50-result clamp, which is useful, but omits any auth, rate-limit, or result-shape context. Adequate against the lower annotation bar but not rich.

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?

Front-loads the purpose, then parameters, then sibling routing in three compact sentences. Slight waste in restating count details that already live in the schema.

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?

With an output schema present and read-only annotations, return values and safety need no description. The keyword/pagination usage is sufficiently covered; only marginal behavioral context (rate limits, ordering) is missing.

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 the baseline is 3. The description repeats the count clamp/default already documented in the schema and adds no new syntax or format meaning for keyword or cursor.

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+resource ('Searches TikTok videos by keyword') and explicitly distinguishes itself from the sibling tiktok_search_user. An agent can tell it apart from the other tiktok_* tools without opening a 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?

Names the alternative tiktok_search_user and the condition that selects it (searching users vs. videos). Clear routing context, though it offers no exclusions or broader when-to-use framing beyond this one sibling.

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

All Crawlora MCP tools Inspect

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

Need Help?