Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_video_transcript

Retrieve a TikTok video's existing captions as WebVTT with timed segments by URL, optionally selecting a language, to obtain transcript text without paid transcription.

Instructions

tiktok: Transcript. GET /v1/tiktok/video/transcript. Get a TikTok video's own captions (TikTok's speech recognition or the creator's), as WebVTT and timed segments. No paid transcription. No captions in the language costs 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when transcript is empty. 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_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTikTok video URL
languageNoTwo-letter language code, such as en or es. Defaults to the video's original captions.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the response format, that no paid transcription is performed, credit cost on success (1), cost on empty or failed results (0), and that cache hits are free. It omits auth/permission expectations and rate limits, 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.

Conciseness3/5

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

The lead sentence is well front-loaded and informative, but the pricing block runs five sentences with overlap: 'Costs 0 credits when transcript is empty' is restated in the closing sentence about not-found or empty results. The billing detail crowds out more useful routing 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 read-only, three-parameter tool with no output schema, the description covers the return format, the cost model, and failure modes well enough to call it confidently. The remaining gaps are authentication expectations and any guidance on choosing the language or cache parameters, which are minor given the schema's own coverage.

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 all three parameters are already documented in the input schema, which sets the baseline at 3. The description adds only an indirect pointer that language selection ties to caption availability ('No captions in the language costs 0 credits'), and cache behavior ties to cache_max_age, but it does not clarify the defaulting semantics beyond what the schema already states.

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 gives a specific verb and resource ('Get a TikTok video's own captions') and even names the payload shape (WebVTT plus timed segments), which tells an agent exactly what comes back. It also carves out scope by excluding 'paid transcription,' though it never explicitly contrasts itself with the adjacent youtube_video_transcript or other transcript siblings, leaving that separation to the name.

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 statement of when to pick this tool over alternatives, nor any when-not-to-use condition beyond 'not for paid transcription.' The only conditional guidance is about pricing tiers based on caption availability, which is billing behavior rather than task routing.

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