yt-dlp-mcp
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
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_video_infoA | Look up metadata for a video URL (YouTube and hundreds of other sites via yt-dlp) without downloading it. Returns title, uploader, duration, view count, thumbnail, and available video qualities. For playlist URLs, only the first video is inspected. |
| download_videoA | Download a video from a URL (YouTube and hundreds of other sites via yt-dlp) to disk. Saves into ~/Downloads by default. Refuses playlist URLs unless allow_playlist is set, to avoid downloading an entire playlist by accident. yt-dlp must be installed separately and reachable on PATH. |
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 2 tools
The two tools have completely distinct purposes—one retrieves metadata, the other downloads content—with no overlap in functionality.
Both tool names follow a consistent verb_noun pattern (download_video, get_video_info), making them predictable and easy to distinguish.
With only two tools, the set is minimal but sufficient for its core purpose of retrieving video info and downloading. A few more utility tools might enhance coverage, but the count is reasonable for a focused wrapper.
The tools cover the two primary actions (metadata retrieval and download) but lack features like format selection or playlist handling (only via flag). Gaps are minor given the scope.