Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_search_tabs

Retrieve the mobile search tabs available for a TikTok keyword, returning keys such as general, video, photos, user, music, live, place, and hashtag plus the is_failed flag.

Instructions

Search tabs available for a keyword. Returns the tab keys the mobile search screen offers for a keyword (general, video, photos, user, music, live, place, hashtag), plus the gateway's is_failed flag. Measured on the mobile search edge with a form POST.

Input Schema

NameRequiredDescriptionDefault
keywordYesSearch keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the returned tab keys, the gateway's is_failed flag, and that the call is measured on the mobile search edge with a form POST. However, it does not explicitly state read-only behavior, side effects, auth needs, or rate limits.

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-loads the main purpose before listing return details. Every clause contributes useful information, though the final sentence about measurement context is somewhat technical and slightly less essential for tool selection.

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 low-complexity, one-parameter search tool with full schema coverage and no output schema, the description is largely complete. It names the returned tab keys and the is_failed flag, which compensates for the missing output schema, though it does not explain what is_failed means.

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 single keyword parameter is already documented in the schema. The description mentions 'keyword' but adds no syntax, formatting, or selection semantics beyond what the schema provides, so baseline 3 is appropriate.

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 action and resource: retrieve search tabs available for a keyword on the TikTok mobile search screen. It also enumerates the tab keys returned, making the tool's purpose clear. It does not explicitly contrast itself with sibling search tools such as tiktok_mobile_search, so it stops short of a 5.

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?

The description implies usage by saying it searches tabs available for a keyword, but it gives no explicit guidance on when to use this tool versus sibling tools like tiktok_mobile_search or tiktok_mobile_search_suggestions. There are no exclusions, prerequisites, or alternatives named.

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