YouTube Content Extractor 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract-youtubeA | Extract comprehensive content from YouTube videos including title, description, and transcript. Automatically uses available subtitles with language priority or falls back to optimized Whisper speech-to-text conversion with language detection. |
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 ambiguity or overlap between tools. The single tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'extract-youtube' follows a clear verb-noun pattern.
One tool is too few for a server named 'YouTube Content Extractor MCP', which suggests a broader scope. The tool only extracts content, lacking operations like search, list, or manage videos, making the set feel incomplete and thin for the domain.
The server is severely incomplete for YouTube content extraction. It only provides extraction, with no tools for discovering videos (e.g., search, list channels), managing data, or handling metadata updates, creating significant gaps in typical workflows.