Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_music_beats

Fetch TikTok mobile music beats chart data as clean JSON, including sound IDs, titles, artists, albums, cover images, and user counts.

Instructions

Retrieve TikTok music beats. Returns the mobile app's beats/songs chart unmodified: music_list of the same full sound objects the pick chart returns (id_str, title, user_count, album, artists, cover_*), ordered as the app's beats list. The measured envelope carries no paging fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoAccepted for compatibility; not measured to change the page (max 50)

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?

With no annotations, the description carries the burden and delivers real behavioral facts: the chart is returned "unmodified," "ordered as the app's beats list," and "the measured envelope carries no paging fields," which tells the agent not to attempt pagination. It stops short of stating auth requirements or the default item count.

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?

Three sentences, front-loaded with the core action, then payload detail, then the paging caveat. Dense but every sentence carries information; minor jargon ("measured envelope") is the only friction.

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 zero-required-parameter chart fetch with no output schema, the description adequately covers return shape, ordering, absence of paging, and the inert count parameter. Default result size and any auth/permission expectations are the remaining gaps.

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% and the single `count` parameter is already documented in the schema as compatibility-only and non-page-affecting. The description reinforces the no-paging behavior but adds no syntax or meaning beyond the structured field, so the baseline of 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 and resource: "Retrieve TikTok music beats," and describes the returned payload concretely (music_list of sound objects with id_str, title, user_count, album, artists, cover_*). It does not, however, differentiate itself from the many sibling charts (tiktok_mobile_music_pick, _trending, _collections), beyond a passing reference to the pick chart's object shape.

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?

There is no explicit when-to-use guidance and no routing against the sibling music charts. The mention that it returns "the same full sound objects the pick chart returns" implies a relationship but never states which chart an agent should choose under which condition.

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