Skip to main content
Glama

YouTube video transcript

youtube_transcript
Read-onlyIdempotent

Get what is said in a YouTube video: its transcript in any language the video has captions in (human-made captions before auto-generated ones), with its title, channel, length, the language returned and every available language. format=text (default) gives the plain text; format=segments gives timed lines with start and duration in seconds. A very long transcript is cut at a line to keep the answer small, and the answer then names the start_seconds to call again with to read on. Videos without captions have no transcript.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA YouTube video link (watch, youtu.be, Shorts, live or embed link) or its 11-character id (_T8cn2J13-4).
langNoA language code (en, es, pt-BR, zh-Hans). Leave it out for the default captions, usually the spoken language. Without captions in that language, the default ones are returned.
formatNotext: the plain transcript. segments: timed lines (start and duration in seconds).text
start_secondsNoRead from this point of the video, in seconds. Used to continue a transcript that was cut.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, non-destructive read, but the description adds real behavioral detail beyond them: caption-source preference order, line-boundary truncation of long transcripts, the continuation contract via start_seconds, and the failure case for videos with no captions.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the core action, then format behavior, then the truncation and no-captions edge cases. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read tool with no output schema, the description covers what is returned (title, channel, length, language, available languages), how output varies by format, and what happens on long or captionless videos. An agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description still adds meaning by explaining the caption-selection preference behind lang and by tying start_seconds to the truncation behavior rather than just describing it as an offset. The format explanation largely restates the enum description.

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?

Opens with a specific verb and resource: 'Get what is said in a YouTube video: its transcript.' The scope (captions, not metadata) cleanly separates it from the sibling youtube_video without needing to name it.

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?

Gives clear operational context: human captions preferred over auto-generated, omit lang for default captions, fall back to defaults if the requested language is missing, and use start_seconds to continue a cut transcript. It does not explicitly route the agent to alternatives (e.g., youtube_video for metadata, youtube_comments for discussion), so it stops short of 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