Skip to main content
Glama

YouTube Video Summarizer (pay-per-call)

get_youtube_transcript

Fetch the raw transcript text of a YouTube video (no model run, the cheaper SKU, $0.003 USDC on Base), in any of 100+ languages (language param, BCP-47). Pay-per-call via x402, no account. A video without captions returns an error and is not charged.

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": "get_youtube_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description takes on the full behavioral burden and does well: it discloses the payment model (x402 pay-per-call, no account), the exact price ($0.003 USDC on Base), and the failure-and-no-charge behavior for captionless videos. It does not describe the shape of the returned text (plain text vs. timed segments) or whether it is truncated for long videos, which for a transcript tool is a meaningful remaining gap.

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?

Purpose is front-loaded and the parentheticals each carry useful facts (cost, payment rail, error case) rather than filler. It is dense but every clause earns its place; only the parenthetical stacking makes it slightly harder to scan than a 5 would require.

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 simple two-parameter read tool with no output schema, the description covers price, payment mechanics, language format, and the error case — enough to call it correctly and anticipate the charge. The missing piece is what the returned transcript looks like structurally, which matters given no output schema exists.

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 0%, so the description must carry both parameters. It adds real meaning for 'language' (BCP-47, 100+ languages), but says nothing about the 'url' parameter's expected format — full watch URL vs. video ID — which is exactly the sort of ambiguity an agent hits when calling. Partial compensation, so a 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Fetch the raw transcript text of a YouTube video') and immediately scopes it against the model-based sibling by saying 'no model run, the cheaper SKU.' An agent can distinguish this from summarize_youtube_video without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context for when this is the right choice: raw text rather than a model-processed result, at a lower price. It also gives a failure condition ('a video without captions returns an error and is not charged'). It stops short of naming the summary alternative explicitly or stating an exclusion rule, so it is strong but not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources