Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_music_pick

Retrieve TikTok sound chart picks and mobile app music lists with pagination. Returns full sound objects, chart lists, and cursors for building music discovery features.

Instructions

Retrieve TikTok sound chart picks. Returns the mobile app's sound pick/chart list: music_list of full sound objects (id, title, author, user_count, duration, ...) plus the chart list mc_list and radio_cursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoSounds per page (max 50)
cursorNoPagination cursor

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 full burden. It does disclose the return shape (music_list with id/title/author/user_count/duration, plus mc_list and radio_cursor), which is genuinely useful, but it omits pagination semantics and any auth or rate-limit 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?

Two tight sentences: purpose first, then return structure. No filler. The parenthetical field list is slightly dense but front-loads the key information effectively.

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, the description appropriately compensates by naming the top-level return fields and their contents. It is complete enough to call the tool, with the only gap being pagination behavior around cursor.

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 (count, cursor) are already documented in the schema. The description adds no parameter detail beyond the loosely related 'radio_cursor' return field, so the baseline 3 holds.

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 ('Retrieve') and resource ('TikTok sound chart picks'), then enumerates the returned structures. However, it doesn't distinguish itself from close siblings like tiktok_mobile_music_trending or tiktok_mobile_music_collections, so an agent must infer the difference from the name alone.

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 and no mention of alternatives, which matters given the dense cluster of tiktok_mobile_music_* siblings. The description describes content but never says under what conditions this tool should be chosen over them.

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