YouTube DLP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_URL | No | Proxy URL for HTTP/HTTPS/SOCKS proxy (optional) |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-video-infoB | Extract detailed information from a YouTube video URL without downloading |
| get-video-subtitlesB | Extract subtitles and captions from a YouTube video |
| get-top-commentsA | Extract top comments from a YouTube video (sorted by likes) |
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 3 tools
Each tool targets a clearly distinct data type: video metadata, subtitles, and comments. There is no overlap in purpose or expected output.
All three tool names follow the exact same 'get-video-<detail>' pattern with consistent hyphenated lowercase naming. The convention is uniform and predictable.
Three tools is on the lower end but each one earns its place for a focused YouTube metadata extraction server. The scope is narrow yet coherent.
Despite the server name referencing 'DLP' (download), there is no download or format-listing tool. The set only covers metadata, subtitles, and comments, leaving a significant gap for a server that implies downloading capability.