Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_song

Fetch TikTok song or sound details using a clip ID from a /music/ URL. Returns metadata for that sound and bills one credit only when the request succeeds.

Instructions

tiktok: Get Song Details. GET /v1/tiktok/song. Get details for a TikTok sound or song. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "clipId": "<clipId>"
    },
    "name": "tiktok_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYesTikTok sound clip ID (clipId), not songId: the trailing number in a /music/ URL. The /music/ URL itself is accepted too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose real behavioral detail that the schema cannot: cost of 1 credit on success and the free cases (errors, blocked, timeouts, invalid requests, cache hits). However, it says nothing about what the response contains, whether the lookup is cached/fresh, or any auth or rate-limit considerations.

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?

It is front-loaded and short overall, with the purpose stated first. The billing caveats take two sentences and partially repeat the 'costs nothing' idea, which is slightly padded but not harmful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema and no annotations, the billing model is well covered, but the description leaves the return payload shape and any failure semantics beyond cost unaddressed. Adequate rather than 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 description coverage is 100% and the single clipId parameter is already documented in the schema, including the important 'clipId, not songId' distinction and URL acceptance. The description adds no parameter meaning beyond the schema, 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?

The description names a specific verb and resource: 'Get details for a TikTok sound or song', reinforced by the concrete endpoint 'GET /v1/tiktok/song'. An agent can distinguish it from feed/search/profile siblings, though it never explicitly contrasts with the closest sibling 'tiktok_song_videos'.

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 when-to-use guidance, no prerequisite conditions, and no named alternative such as the sibling that lists videos for a sound. The agent must infer from the resource noun alone that this is the lookup-by-clipId tool rather than the listing tool.

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