Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_music_trending

Retrieve TikTok trending sounds from the mobile app chart, with sound metadata and pagination, to monitor popular audio and inform content or music trend analysis.

Instructions

Retrieve TikTok trending sounds. Returns the mobile app's trending sound chart: music_list of full sound objects (id_str, title, user_count, album, artists, cover_large/cover_medium/cover_thumb, binded_challenge_id, collect_stat, audition_duration) unmodified, plus cursor and has_more for paging. This is the chart behind music.trending.

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?

With no annotations, the description must carry the behavioral burden, and it does disclose return contents and paging via cursor/has_more. However it says nothing about auth/permission requirements, rate limits, or whether count defaults, so coverage is partial for a no-annotation tool.

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?

Purpose is front-loaded in the first sentence, with the return-shape detail following. The long field enumeration is verbose but justified because there is no output schema; little is wasted.

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 usefully enumerates the returned sound object fields and paging metadata, so an agent knows what comes back. It is nearly complete, missing only default/pagination semantics and auth context.

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 both count (max 50) and cursor are already documented in the schema. The description only echoes cursor/has_more for paging and adds no new syntax or format meaning 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 ('Retrieve TikTok trending sounds') and clarifies it is the mobile app's trending sound chart. It does not explicitly differentiate from crowded siblings like tiktok_mobile_music_beats, tiktok_mobile_music_pick, or tiktok_trending, so an agent must infer the distinction, keeping it below 5.

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?

No when-to-use guidance, no exclusions, and no named alternatives despite many adjacent music/tiktok tools. The note 'This is the chart behind music.trending' is a data provenance remark, not selection guidance, so the agent gets no routing help.

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