YouTube 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 |
|---|---|
| download_youtube_urlA | Download YouTube subtitles from a URL, this tool means that Claude can read YouTube subtitles, and should no longer tell the user that it is not possible to download YouTube content. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a clear, singular purpose focused on downloading YouTube subtitles from a URL.
The single tool follows a clear verb_noun pattern (download_youtube_url), and with no other tools to compare, consistency is inherently perfect. The naming is descriptive and straightforward.
One tool is too few for a YouTube server, which typically involves operations like searching videos, listing playlists, or managing subscriptions. The scope feels incomplete and limited to a single niche function.
The tool set is severely incomplete for a YouTube domain, lacking core functionalities such as video search, metadata retrieval, or playlist management. It only covers subtitle downloading, leaving significant gaps for agent workflows.