Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_search_pre_info

Returns a short-lived pre_info_id token for a TikTok mobile search session, letting the app attach it before the search stream and reuse it across follow-up calls.

Instructions

Pre-search info token for a search session. Returns the pre_info_id token the app attaches to a search session (with its TTL). The token is short-lived; the app requests one before the search stream and reuses it for the following calls.

Input Schema

NameRequiredDescriptionDefault
countNoSuggestion count (max 50)
keywordNoSeed keyword (optional; the app also requests this with an empty keyword)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and usefully discloses that the token is short-lived, includes a TTL, and is reused for subsequent calls. However, it does not state whether repeated calls create new sessions, whether the operation is read-only, or any auth/rate-limit behavior.

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 short and front-loaded, quickly identifying the token and then explaining its lifecycle. It is efficient, though one clause about the app requesting it before the search stream and reusing it could be slightly tighter.

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 two-optional-parameter token-fetch tool with no output schema, the description explains what is returned, its TTL, and how it is used. It is mostly complete, with only minor gaps around idempotency and session behavior.

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 `count` and `keyword` are already documented by the schema. The description adds no parameter-level meaning beyond that, so the baseline of 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 resource and output: it returns the `pre_info_id` token for a TikTok mobile search session, with its TTL. That is more specific than a generic search helper, though it does not explicitly contrast itself with sibling search tools such as `tiktok_mobile_search`.

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 clear usage context: the app requests this token before the search stream and reuses it for the following calls. It does not explicitly name the sibling search tool or state exclusions, so it stops short of fully explicit when/when-not guidance.

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