Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_song_videos

Fetch TikTok videos that use a specific song by sound clip ID, and page through results with the cursor parameter.

Instructions

tiktok: TikToks using Song. GET /v1/tiktok/song/videos. Get the TikToks using a 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

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

Input Schema

NameRequiredDescriptionDefault
clipIdNoTikTok sound clip ID: the trailing number in a /music/ URL, such as 7370375686554782506.
cursorNoThe cursor to get the next page of results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the credit cost model, including success, error, timeout, invalid request, cache hit, and empty-result billing behavior, but omits authentication needs, rate limits, pagination behavior, and return-format details.

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

Conciseness3/5

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

The description is front-loaded with the main purpose, but it repeats the same idea in 'TikToks using Song' and 'Get the TikToks using a song.' The long billing sentence is useful but could be tighter, and the endpoint line adds limited value.

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?

The tool is a simple two-parameter read operation with full schema coverage, and the description adequately explains purpose and cost behavior. However, without an output schema, it does not describe the return shape or pagination behavior, leaving some contextual 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 description coverage is 100%, so the schema already documents both clipId and cursor. The description adds no additional parameter semantics beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: 'Get the TikToks using a song,' and names the endpoint. This clearly identifies the operation, though it does not explicitly distinguish it from siblings such as tiktok_song.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. Usage is only implied by the clipId parameter in the schema.

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