youtube-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUTUBE_API_KEY | No | YouTube Data API v3 key. Required for get_video_info, get_channel_info, and search_videos. Without it, only get_transcript works. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_transcriptA | Extract transcript/subtitles from a YouTube video. Works without API key. |
| get_video_infoA | Get metadata for a YouTube video including title, description, view count, likes, and more. |
| get_channel_infoA | Get information about a YouTube channel including subscriber count, video count, and recent uploads. |
| search_videosA | Search for YouTube videos by keyword. |
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 4 tools
Each tool targets a distinct resource: transcript, video metadata, channel info, and search results. There is no overlap or ambiguity between them.
Most tools follow the get_<resource> pattern (get_transcript, get_video_info, get_channel_info), with search_videos as a minor deviation. The naming is still clear and predictable, but not perfectly uniform.
The server has 4 tools, which is well-scoped for a YouTube info retrieval MCP. Each tool serves a clear and necessary purpose without redundancy.
The coverage is solid for a read-only YouTube API: search, video info, channel info, and transcripts. Minor gaps like playlist support or comments are not core to the apparent purpose, so agents can work around them.