Skip to main content
Glama

Get YouTube transcript

get_youtube_transcript
Read-only

Fetch the full text transcript of a YouTube video. Accepts a YouTube URL (watch, youtu.be, shorts, embed) or a bare 11-character video ID, and returns the transcript as plain text with title and metadata. Optionally pass a BCP-47 language code to select a specific caption track. Very long transcripts (multi-hour videos) come back in parts of up to 120,000 characters: when there is more, the result ends with a note giving the offset to pass on the next call.

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": {
      "video": "<video>"
    },
    "name": "get_youtube_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOptional BCP-47 language code, e.g. "en", "zh-CN", "es". Omit for the default track.
videoYesYouTube video URL or 11-character video ID
offsetNoOptional. Character position to continue a long transcript from. Use the value given in the note at the end of the previous part. Omit to start from the beginning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Optional. Character position to continue a long transcript from. Use the value given in the note at the end of the previous part. Omit to start from the beginning.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely new behavior: the return is plain text plus title/metadata, and long transcripts are chunked at 120,000 characters with a trailing note supplying the next offset. It omits failure behavior (videos with no captions, private/region-blocked videos), which keeps it below 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?

Purpose is front-loaded in the first sentence, followed by input formats, language selection, and pagination in a logical order. The BCP-47 sentence is somewhat redundant with the schema but is short enough not to be wasteful.

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?

With no output schema, the description takes on return-shape duty and does so (plain text plus title and metadata, chunked with offset continuation). For a single-resource read tool this is nearly sufficient; only error/no-caption cases are left 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%, and the description largely restates what the schema already says about lang, video formats, and offset. It does tie offset to the end-of-part note, which adds a little operational meaning, but with the schema doing the heavy lifting a baseline 3 is appropriate.

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 full text transcript of a YouTube video') and spells out accepted input forms (watch, youtu.be, shorts, embed URLs or a bare 11-char ID). Combined with the pagination detail, an agent can distinguish this bulk-fetch tool from section- or search-oriented siblings without opening a schema.

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 context is implied: this is the tool for pulling a whole transcript, and offset is for continuing a long one. However, it never names an alternative such as get_transcript_section or find_in_transcript, nor does it state when not to use it (e.g., when only a fragment or a keyword match is needed).

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.