Youtube To Mp315 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusC | Check the status of the file conversion |
| downloadC | Convert YouTube video to mp3 async |
| titleB | Get the title of YouTube video |
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 has a clear, distinct purpose: download initiates conversion, status checks progress, and title retrieves video metadata. No overlap or ambiguity.
All tool names are single lowercase verbs that accurately describe their actions, maintaining a consistent and predictable pattern.
With only three tools, the server is tightly scoped to the core workflow of YouTube-to-MP3 conversion, avoiding unnecessary bloat.
The tool set covers the essential lifecycle: initiating a download, checking its status, and fetching title info. No critical gaps for the stated purpose.