Skip to main content
Glama
granitebps

YouTube MCP Server

by granitebps

get_video_transcript

Retrieve YouTube video transcripts with timestamps in any supported language. Returns both timestamped and plain text versions, with pagination for long transcripts.

Instructions

Get YouTube video transcript/captions (manual or auto-generated) with timestamps. Use 'lang' to specify language code (e.g. 'en', 'id'). Returns both timestamped and plain text versions. Returns error if captions are unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLanguage code for the transcript (e.g., 'en', 'id', 'ja')en
videoYesYouTube video URL or video ID
maxSegmentsNoMaximum number of transcript segments to return. 0 (default) returns all segments. Use with startSegment for pagination.
startSegmentNoSegment index to start from (0-based). Use with maxSegments to paginate through long transcripts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hasMoreYes
messageNo
videoIdYes
segmentsYes
availableYes
plainTextYes
languageCodeYes
startSegmentYes
totalSegmentsYes
nextStartSegmentYes
returnedSegmentsYes
Behavior4/5

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

No annotations provided, so description must disclose behavior. It reveals it returns both timestamped and plain text versions, supports auto-generated and manual captions, and errors if captions are unavailable. This is good coverage, though it doesn't mention rate limits or auth requirements.

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?

Two concise sentences, no fluff, front-loaded with primary purpose. Every word earns its place.

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?

Given the presence of an output schema, the description need not detail return values. It covers key aspects: source (YouTube video), type (transcript/captions), and error case. Lacks mention of pagination support but that is handled by parameter descriptions.

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 100%, so the schema already documents all parameters. Description adds minimal extra meaning beyond what schema provides (e.g., language code examples). 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?

Description clearly states it gets YouTube video transcript/captions with timestamps. It distinguishes from sibling tools like get_transcript_languages (which lists languages) and get_video_comments (which gets comments).

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?

Description mentions language code specification and error behavior but does not explicitly guide when to use this tool vs alternatives like get_transcript_languages for listing available languages. Usage context is implied but not explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/granitebps/youtube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server