Skip to main content
Glama
fetchtranscript-mcp

fetchtranscript-mcp

Official

get_transcript

Retrieves a YouTube video’s transcript by video ID in text, timestamped JSON, or SRT format, with automatic language detection when no language code is provided.

Instructions

Get the transcript of a YouTube video.

Args: video_id: YouTube video ID (11 characters, e.g. 'dQw4w9WgXcQ') lang: Language code (e.g. 'en', 'it'). Auto-detected if omitted. format: Output format — 'text' (default), 'json' (segments with timestamps), or 'srt'.

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_id": "<video_id>"
    },
    "name": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
formatNotext
video_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add real value by naming the three output formats with a stated default and explaining that language is auto-detected, but it says nothing about failure modes (missing/unavailable transcript), auth needs, or rate limits.

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?

The Args-style layout is compact and front-loads the one-line purpose before the parameter list. Every line carries information; only the mild restatement of the tool name in the opening sentence is slightly redundant.

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?

An output schema exists, so return values need not be explained, and the format parameter already signals output shape. What is missing for a tool of this simplicity is only the edge-case behavior when no transcript exists.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate entirely, and it does: it specifies the 11-character video ID format with an example, gives concrete language code examples, and enumerates the format values ('text', 'json' with timestamps, 'srt') plus the default. This meaning is absent from the raw schema, where 'format' is an unconstrained string.

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 ('Get') and resource ('the transcript of a YouTube video'), which is enough to separate it from siblings like get_chapters, get_comments, or get_video_metadata. It stops short of an explicit 'this is not X' statement, so it lands at clear-but-not-differentiating.

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 statement of when to use this tool versus alternatives, and no prerequisites such as whether the video must have captions available. The only contextual hint is that 'lang' is auto-detected if omitted, which is parameter behavior rather than usage guidance.

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