Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

tiktok_mobile_search_pre_info

Read-only

Retrieve pre-info response data for a TikTok search session. The keyword is optional; use the short-lived token with the app's search flow.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_mobile_search_pre_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoRequested result count, maximum 50.
keywordNoOptional keyword for the TikTok search session; an empty keyword is accepted.

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. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds only that this is part of a search flow with a short-lived token. It does not explain what "pre-info" fetches, whether it is a required preliminary step, or what prerequisites exist, and the token reference conflicts with the visible parameter set.

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?

The description is two short sentences and is front-loaded with the intended operation. There is little waste, though the second sentence's token reference is not grounded in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even with an output schema and annotations, the description leaves the core concept of "pre-info" unexplained and gives no guidance on when this tool is needed versus the actual search tool. For an obscure flow-specific tool, this is not enough for reliable selection.

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%, so both `count` and `keyword` are fully documented in the schema. The description only repeats that `keyword` is optional and adds no syntax, default, or behavioral meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description essentially restates the tool name: "Retrieve pre-info response data" does not explain what "pre-info" means or what data is actually returned. It mentions a TikTok search session, but an agent cannot tell how this differs from sibling tools like tiktok_mobile_search, tiktok_mobile_search_suggestions, or tiktok_mobile_search_tabs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says the keyword is optional and refers vaguely to "the app's search flow," but gives no condition for choosing this tool over the many other TikTok search tools. The mention of a "short-lived token" is not actionable because no token parameter exists in the schema.

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

All Crawlora MCP toolsInspect
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