Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_search_user

Search TikTok users by keyword and paginate matches with a cursor. Returns user_list plus cursor and has_more to fetch the next page.

Instructions

Search TikTok users. Searches TikTok users for keyword, with cursor (default 0) for paging. The response has user_list with the matching accounts, plus a cursor and has_more to continue. Pass the returned cursor back to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor
keywordYesSearch keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It helpfully describes the response shape (user_list, cursor, has_more) and pagination behavior, but it does not mention read-only nature, authentication, rate limits, or any caveats about result scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences, front-loaded with the tool's purpose, then pagination inputs and outputs. Every sentence adds useful information with no filler.

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

Completeness3/5

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

Given no output schema, the description adequately explains the return fields and paging. However, for an agent choosing among many TikTok-related tools, it lacks differentiation from the very similar tiktok_mobile_search_user sibling, leaving a routing ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds useful meaning by explaining that cursor defaults to 0 and should be reused from the prior response to fetch the next page. This clarifies the pagination workflow beyond the schema's terse 'Pagination cursor'.

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 verb and resource: search TikTok users for a keyword. It is clear what the tool does, but it does not distinguish this tool from close siblings such as tiktok_mobile_search_user or tiktok_profile.

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?

The description implies usage for user search and explains pagination continuation via the cursor. However, it gives no explicit guidance on when to use this instead of sibling tools like tiktok_mobile_search_user, tiktok_profile, or general tiktok_search.

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