yt-consolidado
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUTUBE_API_KEY | No | Single YouTube Data API v3 key, accepted as an alternative to YOUTUBE_API_KEYS. Required for the Data API tools. | |
| YOUTUBE_API_KEYS | No | Comma-separated pool of YouTube Data API v3 keys, rotated when quota is exceeded. Required for the Data API tools. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_videosB | Search videos/channels/playlists — port of youtube-mcp |
| youtube_searchC | Search with date/channel/duration filters — port of tube-bridge |
| search_channelsC | Search channels enriched with stats — port of youtube-mcp |
| get_channel_detailsB | Channel metadata by id/@handle/username — port of youtube-mcp. |
| find_breakout_creatorsC | New channels with subscriber velocity — port of youtube-mcp |
| channels_getChannelB | Raw channel + normalizedMetadata — port of youtube-mcp-server (zubeid). |
| get_channel_rss_videosB | Latest uploads from the Atom feed — port of youtube-mcp |
| youtube_get_video_infoC | Rich metadata for one video — port of tube-bridge |
| youtube_get_channel_videosB | Recent uploads via yt-dlp — port of tube-bridge |
| youtube_get_transcriptC | Video transcript — port of tube-bridge |
| get_first_published_dateC | Oldest publication date of a channel. Did not exist in any original. |
| max_views_in_channelA | Highest view count among uploads since |
| avg_durationB | Mean duration of the last N uploads. New tool. |
| find_emerging_channelsB | Emerging channels by composite filters — the product tool. |
| get_quota_statusA | Session quota ledger: units spent per tool and per endpoint, layers used. |
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 15 tools
Several tool pairs have near-identical purposes: search_videos vs youtube_search (both video search, one with filters/fallback), get_channel_details vs channels_getChannel (both channel metadata by id/handle), and get_channel_rss_videos vs youtube_get_channel_videos (both 'recent uploads of a channel'). Descriptions explain layer/quota differences, but an agent choosing by intent alone would frequently misselect, and find_breakout_creators vs find_emerging_channels vs search_channels further blur the discovery space.
Conventions are mixed: some tools carry a youtube_ namespace prefix (youtube_search, youtube_get_video_info), others are bare snake_case (search_videos, avg_duration), and one is camelCase with a resource prefix (channels_getChannel). Verb styles also vary (get_/find_/search_/avg_/max_), so the name gives little predictable signal about which layer or operation a tool uses.
15 tools is at the upper edge of the reasonable band and the count is inflated by near-duplicate ports (two search tools, two channel-detail tools, two recent-uploads tools) rather than by distinct capabilities. A consolidated surface would need roughly 10-11 tools for the same coverage.
Coverage is broad for a YouTube data-collection server: search, channel/video metadata, transcripts, RSS, channel analytics (avg duration, max views, first publish date), discovery, and quota accounting. Gaps exist around playlists (only searchable, no playlist fetch/list) and comments, but core workflows are reachable.