Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_music_related

Find sounds related to a TikTok video using its video ID. Returns sound objects, recall reasons, similar song IDs, and cursor/has_more for pagination.

Instructions

Retrieve sounds related to a TikTok video. Returns sounds related to one video: music_list of full sound objects, recall_info_list explaining why each was recalled, similar_song_ids, plus cursor and has_more.

Input Schema

NameRequiredDescriptionDefault
countNoSounds per page (max 50)
cursorNoPagination cursor
aweme_idYesVideo id to find related sounds for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does disclose the return structure (music_list, recall_info_list, similar_song_ids, cursor, has_more) — valuable since there is no output schema. It still omits whether the call is read-only, any auth requirements, or rate limits, but 'Retrieve' plus the field list gives solid transparency.

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, purpose front-loaded, then return fields. The enumerated return fields are justified given the absence of an output schema, and there is little wasted text.

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?

For a read-style, three-parameter tool with no output schema and no annotations, the description covers the essential purpose and the shape of the response. It leaves pagination semantics and the meaning of recall_info_list somewhat under-explained, so it is not fully complete.

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 count, cursor, and aweme_id are already documented in the schema, and the description adds no syntax or format detail beyond that. Baseline 3 is appropriate since the schema does the heavy lifting.

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 (sounds related to a TikTok video), which lets an agent distinguish it from siblings like tiktok_mobile_music_trending or tiktok_mobile_music_pick. However, it never names or contrasts those alternatives explicitly, so sibling differentiation is left to inference.

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?

The phrase 'related to a TikTok video' implies the tool is anchored on a specific video id, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternative sound-discovery siblings. The agent gets context but no routing instructions.

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