Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_search_suggestions

Retrieve TikTok mobile search suggestions for a seed keyword to expand queries and see phrases the app associates with that term.

Instructions

Retrieve TikTok search suggestions. Returns the mobile app's search typeahead for a seed keyword: sug_list of suggestions, each with content, sug_type, word_record (group_id, words_position, words_content, words_source) and positional fields, unmodified. Useful for query expansion and for seeing the phrases the app itself associates with a seed term. keyword is required; without it the upstream answers a well-formed but empty envelope.

Input Schema

NameRequiredDescriptionDefault
countNoSuggestions to return (max 50)
keywordYesSeed keyword to expand

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does a creditable job: it discloses the return shape (sug_list with content, sug_type, word_record and positional fields), notes the payload is passed through "unmodified," and warns that a missing keyword yields a well-formed but empty envelope — a non-obvious failure mode that would otherwise be misread as "no results." It stops short of any rate-limit or quota context.

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-loaded with the action, then the return shape, then the use case, then the required-parameter caveat. Dense but readable; the field enumeration (group_id, words_position, words_content, words_source) is the only stretch that borders on reference material rather than guidance.

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 no output schema and no annotations, the description must explain results and edge behavior itself, and it does — it enumerates the response fields, frames them as unmodified upstream data, and covers the empty-envelope case. Missing only count-behavior details and any rate/auth expectations for a tool that hits an upstream endpoint.

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 parameters are already documented (including "max 50" for count). The description adds one genuinely new piece of meaning — the consequence of omitting keyword — but says nothing about count semantics such as default value or what happens when more than 50 is requested. Baseline 3 is right where the schema does the heavy lifting.

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?

Specific verb + resource ("Retrieve TikTok search suggestions") plus a precise characterization of what is returned: the mobile app's search typeahead for a seed keyword. The mention of "mobile app" and "typeahead" distinguishes it from siblings like tiktok_mobile_search, tiktok_search, and the other tiktok_mobile_search_* tools without opening any schema.

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

Usage Guidelines3/5

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

"Useful for query expansion and for seeing the phrases the app itself associates with a seed term" implies the use case but never states when to pick this over tiktok_mobile_search or tiktok_mobile_search_hashtags/effects, nor any exclusion. Adequate for a narrow autocomplete tool but leaves the routing decision to the agent.

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