YouTube Transcript MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| youtube_get_transcriptC | Extract transcript from a YouTube video URL |
| youtube_search_transcriptC | Search for specific text within a YouTube video transcript |
| youtube_batch_transcriptsC | Extract transcripts from multiple YouTube videos |
| youtube_transcript_summaryB | Get a formatted summary of transcript content |
| youtube_get_channel_videosC | Get video list from a YouTube channel |
| youtube_get_channel_video_urlsC | Get video URLs from a YouTube channel |
| youtube_get_channel_transcriptsC | Get transcripts from multiple videos in a YouTube channel |
| youtube_get_playlist_infoC | Get information about a YouTube playlist |
| youtube_get_playlist_videosC | Get video list from a YouTube playlist |
| youtube_get_playlist_video_urlsC | Get video URLs from a YouTube playlist |
| youtube_get_playlist_transcriptsC | Get transcripts from multiple videos in a YouTube playlist |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes targeting different YouTube resources (videos, channels, playlists) and actions (get transcripts, get videos, get URLs, search, summarize). However, youtube_get_channel_videos and youtube_get_channel_video_urls could potentially be confused as both retrieve video information from channels, though one provides lists and the other URLs.
All tools follow a consistent snake_case naming pattern with a clear youtube_ prefix followed by verb_noun structure (e.g., youtube_get_transcript, youtube_search_transcript, youtube_transcript_summary). The naming convention is predictable and readable throughout the entire set.
With 11 tools, the count is reasonable for a YouTube transcript-focused server. It covers multiple aspects of the domain (videos, channels, playlists) but might be slightly heavy with some overlapping functionality (e.g., multiple channel and playlist tools that could potentially be consolidated).
The tool set provides comprehensive coverage for YouTube transcript operations, including extraction from individual videos, batches, channels, and playlists, plus search and summarization capabilities. There are no obvious gaps for the stated purpose of transcript handling, with good lifecycle coverage from retrieval to analysis.