Skip to main content
Glama

tiktok_mobile_music_trending

Read-only

Retrieve TikTok mobile's trending-sounds chart with cursor pagination. Results are the app's current chart, not a historical or worldwide ranking.

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

Input Schema

NameRequiredDescriptionDefault
countNoSounds to request, maximum 50.
cursorNoPagination cursor returned by the previous page.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds that results are the live in-app chart rather than a historical/worldwide ranking, which is genuine behavioral context, but it says nothing about auth, rate limits, or result freshness beyond that single qualifier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, zero filler, and the core capability is front-loaded with the scoping caveat immediately after.

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 needn't be explained, and annotations cover the safety profile. The description is adequate for a two-optional-param chart tool, with only minor room to state pagination limits more precisely.

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 both count and cursor are already documented in the schema. The description mentions 'cursor pagination' but adds no syntax, defaults, or limits beyond what the schema provides, so baseline 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 ('Retrieve') and resource ('trending-sounds chart') and scopes it as the app's current chart. It distinguishes itself conceptually from historical/worldwide rankings, though it doesn't name the specific sibling music tools (e.g. tiktok_mobile_music_pick) it differs from.

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?

The clause 'not a historical or worldwide ranking' implies the appropriate use case (current app chart) but stops short of explicitly naming alternatives or stating when-not conditions. Usage is inferable rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.