Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_search

Search TikTok videos by keyword through the mobile API and return raw JSON results with video details, statistics, and pagination metadata.

Instructions

Search TikTok videos on the mobile API. Keyword search returning the mobile API result documents unmodified: each entry has aweme_info (a full video object with statistics), card_profile and search metadata, plus cursor and has_more. Keep count small (20 already exceeds one megabyte of upstream JSON).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoResults per page (max 20)
offsetNoResult offset
keywordYesSearch keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it enumerates the return shape (`aweme_info`, `card_profile`, `cursor`, `has_more`) and warns that `count=20` already exceeds one megabyte of upstream JSON. It does not mention auth or rate limits, but the payload warning is genuinely useful context an agent cannot get from structured fields.

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?

Two sentences, front-loaded with the core action and return format, closing with an actionable constraint. No filler, and the ordering puts the essential identity first.

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?

No output schema exists, so it is right that the description outlines the return structure, and `cursor`/`has_more` convey pagination implicitly. The gaps are minor: no auth or rate-limit context, and no explicit sibling routing.

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 meaning beyond the schema's terse 'Results per page (max 20)' by explaining that even 20 results blow past a megabyte. That reframes `count` as a real performance lever rather than just a limit.

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 and resource ('Search TikTok videos') and qualifies the scope with 'on the mobile API,' which hints at differentiation from the non-mobile `tiktok_search` sibling. It stops short of naming that alternative explicitly, so the distinction is inferred rather than stated.

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 guidance or comparison against siblings like `tiktok_search`, `tiktok_mobile_search_user`, or `tiktok_mobile_search_music`. The one practical note ('keep count small') governs how to call the tool, not when to choose it over alternatives.

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