youtube-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUTUBE_API_KEY | Yes | Your YouTube Data API v3 key |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_videosC | Search for YouTube videos with various filters |
| search_channelsC | Search for YouTube channels |
| get_video_detailsC | Get detailed information about specific videos |
| get_channel_detailsB | Get detailed information about specific channels |
| get_trending_videosB | Get trending/popular videos for a region |
| get_video_categoriesB | Get video categories for a region |
| get_channel_videosB | Get recent videos from a specific channel |
| get_playlist_videosC | Get videos from a YouTube playlist |
| search_playlistsC | Search for YouTube playlists |
| get_video_commentsC | Get comments for a YouTube video |
| get_channel_by_handleC | Get channel details by handle (@username) |
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, but 'get_channel_details' and 'get_channel_by_handle' overlap in retrieving channel info, differing only by input. Similarly, 'get_video_details' could be confused with results from 'search_videos', though descriptions help.
All tools use consistent snake_case with a verb_noun pattern (get_*, search_*), making the naming predictable and easy to parse for an agent.
11 tools is well-scoped for a YouTube data server, covering channels, playlists, videos, trending, comments, and search without unnecessary bloat.
The set covers major read operations for YouTube data, but misses some lifecycle actions like channel/playlist management, video updates, and comment posting. Gaps are minor for a focused retrieval server.