Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_mobile_music_choices

Fetches the recommended sound list for TikTok video creation, returning full music objects with titles, artists, covers, play URLs, and durations so you can choose audio for a video.

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: 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_mobile_music_choices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses the upstream endpoint, the returned music_list objects, the measured payload size and item count, the absence of paging fields, and the fact that recommendations rotate. It does not mention authentication, rate limits, or other operational constraints, so it is strong but not fully exhaustive.

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?

The description is front-loaded and well structured: purpose first, then return shape, payload behavior, and parameter rationale. It is somewhat long and includes very specific measurement details such as exact byte count and dated observations, which are useful but slightly beyond what most agents need.

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?

For a zero-parameter tool with no annotations and no output schema, the description is complete enough to call and interpret correctly. It explains the return structure, the absence of paging, the one-shot nature of the list, and why no input parameters are exposed.

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?

There are zero parameters, so the baseline is 4. The description adds useful context by explaining that measured item_id, music_id, count, and scene parameters did not deterministically affect the list and were therefore not exposed.

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?

The description clearly identifies the resource: the recommended-sounds list served on TikTok's video-creation page, and it distinguishes this from generic chart routes by describing the return as a one-shot recommendation list. It stops short of explicitly naming ambiguous siblings such as tiktok_mobile_music_pick or tiktok_mobile_music_trending, so sibling differentiation is only partial.

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 by 'recommended sounds for video creation' and 'one-shot recommendation list,' which gives context for when the tool is relevant. However, the description never explicitly says when to use this tool instead of the many other tiktok_mobile_music_* siblings, nor does it state when not to use it.

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