Skip to main content
Glama

tiktok-scraper-video-downloader-api-mcp

Get Sound / Music Track Metadata

tiktok_music_info
Read-onlyIdempotent

Get TikTok sound/music metadata, MP3 playback URL, author, duration, and usage count. Accepts a music ID, music URL, or video URL (10 credits).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "tiktok_music_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTikTok sound ID, sound URL, or TikTok video URL to extract audio from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already state readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds meaningful context beyond them: the 10-credit cost, the accepted identifier forms, and the shape of returned data including a playable MP3 URL.

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 short sentences, front-loaded with purpose and return fields, followed by the cost note. No filler; every clause carries information.

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 single-parameter read tool with full schema coverage and no output schema, listing the principal return fields (MP3 URL, author, duration, usage count) makes the definition largely sufficient. Minor gap: no note on error behavior for invalid IDs or regional restrictions.

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 url parameter is fully described in the schema, matching the description's statement of accepted ID/URL forms. The description adds no format examples or precedence rules beyond what the schema already says, 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?

Names a specific verb+resource (TikTok sound/music metadata) and enumerates the returned data: MP3 playback URL, author, duration, usage count. It effectively distinguishes itself from tiktok_music_posts by describing metadata retrieval, though it never explicitly contrasts with the posts sibling.

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 only implied: it tells you input can be a music ID, music URL, or video URL and that the call costs 10 credits, but gives no explicit guidance on when to prefer this over tiktok_music_posts or tiktok_video_detail.

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.

Resources