Crawlora MCP

tiktok_mobile_music_collections

Read-only

Return TikTok mobile sound collections and their contained music objects. Use this to explore the app's themed sound collections; the response is a measured first page and its cursor is not reusable.

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_collections"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	Collections to request; zero uses the app default, maximum 50.
`cursor`	No	Accepted for compatibility only; the returned cursor is not a verified continuation token.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context absent from annotations: the response is only a "measured first page" and its cursor is "not reusable," which warns the agent about pagination limits.

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 sentences, front-loaded with what the tool returns and then the operational caveat. No filler; every clause contributes.

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?

An output schema exists so return values need no prose, and annotations cover the safety profile. The description supplies the one thing an agent would otherwise get wrong, the one-shot pagination behavior, making it adequate for calling the tool correctly.

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 and cursor are already documented, including that cursor is compatibility-only. The description reinforces the non-reusable cursor caveat but adds no new syntax or format detail beyond the schema. Baseline 3 applies when the schema carries the parameters.

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: returns TikTok mobile sound collections plus their contained music objects, and frames the use case as exploring themed sound collections. This distinguishes it from sibling endpoints like tiktok_mobile_music_posts or tiktok_mobile_music_trending, though it does not explicitly name which sibling to prefer.

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?

Gives a positive use case ("explore the app's themed sound collections") but offers no when-not guidance and never names an alternative within the dense tiktok_mobile_music_* / tiktok_mobile_search_music family. Usage is implied rather than instructed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?