Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_video

Fetch public TikTok video or slideshow data by URL, including media play addresses and optional native captions, to verify content and metadata.

Instructions

tiktok: Video Info. GET /v2/tiktok/video. Get a public TikTok video or slideshow by URL. Not-found does not prove deletion. Video files are in video.play_addr and video.bit_rate[].play_addr. 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": {
      "url": "<url>"
    },
    "name": "tiktok_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTikTok video or photo/slideshow URL
trimNoSet to true to get a trimmed response
regionNoAccepted for compatibility. The US page is read.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.
download_mediaNoNot supported: download_media=true returns 400. Use the play_addr or download_addr URLs in the response.
get_transcriptNoSet get_transcript=true for the video's native captions (WebVTT) at no extra cost. Missing captions return no transcript.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does it well: it discloses the credit cost and exactly which outcomes are free, warns that not-found does not prove deletion, and points to where media URLs live in the response. Auth requirements and rate limiting are not mentioned, keeping it short of a 5.

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?

Front-loaded with the purpose and route, then the important caveats. The final sentence about not-found/empty-result billing is somewhat repetitive after the prior cost sentence, but overall it is tight and readable.

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 6-parameter read tool with no annotations and no output schema, the description covers cost model, caching behavior, failure semantics, unsupported options, and the key response field paths. Only auth/rate-limit expectations are unaddressed.

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 explains url, trim, region, cache_max_age, download_media and get_transcript. The description adds only marginal parameter context (cost implications of cache hits, unsupported download_media), 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 and resource ('Get a public TikTok video or slideshow by URL') and even the underlying route. It is clear what the tool returns, though it does not explicitly contrast itself with transcript or comment siblings.

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 implied by the URL-based fetch and clarified by the cost rules (free on errors, cache hits, blocked requests) and the caveat that not-found does not prove deletion. There is no explicit routing guidance such as when to prefer tiktok_video_transcript or tiktok_video_comments instead.

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