Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_music_choices

Fetches the recommended TikTok sounds list for video creation, returning full sound objects with titles, artists, covers, play URLs, and durations in one call.

Instructions

Recommended sounds for video creation. Returns the app's "music choices" list: the recommended sounds it offers on the video-creation page. The upstream is /aweme/v1/music/choices/; each music_list entry is the same full sound object the chart routes return (title, album, artists, covers, play URL, duration, ...). Measured 2026-10-21 with the pure-Go (device-free) signer: 56,078 B / 6 full sound objects on one call and 7 on later calls (the same six at the front), and the payload carries NO paging fields (no cursor/has_more), so this is a one-shot recommendation list. The measured item_id, music_id, count and scene parameters did not deterministically change the list — the recommendations rotate — so none is exposed. The route is not signature-gated, so it does not need the device-backed signer.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well: it discloses payload size (~56KB, 6-7 full sound objects), that no paging fields exist so it is a one-shot call, that recommendations rotate between calls, and that the route is not signature-gated. These are exactly the non-obvious traits an agent needs.

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?

Front-loaded with the one-line purpose, then progressively deeper detail. It is longer than typical, and the exact byte count (56,078 B) and measurement date are marginally useful, but every sentence still conveys either output shape, behavior, or parameter rationale.

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

Completeness5/5

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

No output schema exists, and the description compensates by describing what each music_list entry contains (title, album, artists, covers, play URL, duration). Combined with the no-paging and rotation caveats, an agent can call this correctly with no missing information.

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?

Zero parameters gives a baseline of 4, and the description goes further by explaining why: item_id, music_id, count and scene were measured and found not to deterministically change the list, so none is exposed. That preempts an agent trying to pass filters.

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 concrete verb+resource: returns the app's 'music choices' recommended sound list shown on the video-creation page, with the upstream route named. It differentiates itself obliquely from chart routes ('the same full sound object the chart routes return') but never names the actual siblings (tiktok_mobile_music_trending, _music_pick, _search_music), so an agent must infer the distinction.

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?

Usage is implied rather than stated: no parameters, one-shot recommendation list, no paging. It never says when to prefer this over tiktok_mobile_music_trending, tiktok_mobile_music_pick, or tiktok_mobile_search_music, so selection guidance is left to the agent.

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