Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_search_user

Search TikTok users by username or display name through the mobile API, returning user lists with follower, following, and engagement statistics for creator research.

Instructions

Search TikTok users on the mobile API. Keyword search over users, returning user_list unmodified. Each user_info carries the populated creator statistics (follower_count, following_count, total_favorited, aweme_count, custom_verify).

Input Schema

NameRequiredDescriptionDefault
countNoUsers per page (max 50)
cursorNoPagination cursor
keywordYesSearch keyword (a username or display name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

B3.2/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. It usefully discloses the return contract ('user_list unmodified' and the creator statistics fields in each user_info), but says nothing about auth requirements, rate limits, or pagination 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?

Two sentences, purpose front-loaded, no filler. The second sentence earns its place by describing the return shape that the absent output schema cannot provide.

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?

With no output schema and no annotations, the description partially compensates by naming the return fields, but it omits pagination semantics and the mobile-vs-standard API distinction that would make the definition complete for this variant.

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 count, cursor, and keyword are already documented. The description adds no syntax or format detail beyond the schema, so baseline 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?

States a specific verb+resource ('Search TikTok users') and adds the 'mobile API' qualifier, which is a real differentiator against siblings like tiktok_search_user and tiktok_mobile_search. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully self-differentiating.

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?

There is no when-to-use/when-not guidance. The 'mobile API' phrase hints at a variant distinction but never tells the agent when to pick this over tiktok_search_user or tiktok_search, leaving the choice to inference.

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