youtube-mcp

get_transcript

Retrieve YouTube video transcripts and subtitles by providing a video URL or ID. Optionally specify language code for localized transcript. No API key required.

Instructions

Extract transcript/subtitles from a YouTube video. Works without API key.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	YouTube video URL or video ID
`lang`	No	Language code for transcript (e.g., 'ko', 'en')	en

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds one non-obvious fact (no API key required) and 'Extract' implies a read operation, but it does not mention return format, rate limits, or error behavior. This is a minimal but not rich disclosure.

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?

A single, front-loaded sentence that states the action and a key context (no API key). Every word earns its place, with no redundancy or filler.

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

Completeness3/5

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

The tool is simple with two parameters and no output schema, so the description must explain return values, but it does not. It states purpose and the no-API-key advantage but leaves the format of the extracted transcript (plain text, timestamps, etc.) unspecified. Adequate for a basic understanding, but incomplete for full autonomous use.

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?

The input schema already documents both parameters (url and lang) with descriptions and a default for lang, so schema coverage is 100%. The description itself adds no extra parameter meaning beyond what the schema provides, so the 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?

The description uses a specific verb ('Extract') with a clear resource ('transcript/subtitles from a YouTube video'). It immediately distinguishes itself from sibling tools like get_video_info, get_channel_info, and search_videos, which handle different resources.

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?

Provides clear context: extracts transcripts and works without an API key, which is a useful selection hint. However, it does not explicitly mention alternatives or state when not to use this tool, so it stops short of full exclusion guidance.

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

Deploy Server