Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_video_transcript

Retrieve publicly available captions or a transcript from a YouTube video or Short by URL, with optional language selection or original-audio captions.

Instructions

youtube: Transcript. GET /v1/youtube/video/transcript. Get publicly available captions or a transcript from a YouTube video or Short 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": "youtube_video_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video or short URL
languageNoCaption language, e.g. en or en-US; original_audio=true overrides it. Omit for automatic selection. No matching requested or identified original-language captions returns null at no charge.
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.
original_audioNoSet true for original-language captions only, overriding language. Unidentified original audio or missing captions returns null at no charge. A returned transcript costs 1 credit; no extra lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 burden and does a solid job: it states 1 credit on success, 0 credits on an empty transcript, and that errors, blocked/timed-out, invalid and cache-hit requests are free. It omits auth requirements, rate limits, and the shape of the returned transcript, so the disclosure is strong on billing but incomplete on other behavior.

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?

Purpose and endpoint are front-loaded, which is good, but the four consecutive cost sentences are repetitive and partly self-cancelling: 'Costs 0 credits when transcript is empty' sits uneasily beside 'A not-found or empty result is charged only where that operation's published cost says so.' That trailing hedge makes the pricing rules harder to apply than they need to be.

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?

Given four parameters, full schema coverage and no output schema, the definition covers purpose and cost adequately. The notable gap is return format: because no output schema exists, the definition should say what a transcript looks like (text only, timed segments, null cases), but it leaves that to the schema's parameter notes.

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 schema itself explains language, cache_max_age and original_audio in more detail than the description does. The description adds no parameter-level meaning beyond what the schema provides, so the 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?

The description names a specific verb and resource: 'Get publicly available captions or a transcript from a YouTube video or Short', plus the underlying route GET /v1/youtube/video/transcript. An agent can tell this retrieves caption text rather than video metadata or comments. It does not explicitly contrast with the closest sibling (youtube_video), so it stops short of full differentiation.

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?

There is no explicit when-to-use or when-not-to-use statement, and no named alternative such as youtube_video for metadata. Usage is only implied by the resource name and by the cost model, which does help an agent decide whether a call is cheap. Adequate but not instructive.

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