YouTube Outlier MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUTUBE_API_KEY | Yes | Your YouTube API key used to access the YouTube Data API. |
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 |
|---|---|
| resolve_channelA | Get a YouTube channel overview: title, handle, subscribers, total views, video count. Accepts @handle, UC... channel id, or channel URL. |
| get_channel_videosA | List a channel's most recent videos with raw YouTube fields (views, likes, comments, duration, publishedAt). Newest first. |
| find_outlier_videosA | ★ Find videos that overperformed vs the channel's own median views (outlier detection). Use it to reverse-engineer which topics/formats worked. Returns raw YouTube fields plus a derived multiplier (marked as non-YouTube data). |
| search_channelsA | Search YouTube channels by keyword. NOTE: the search endpoint has a separate low daily quota, so results are cached. |
| get_trendingB | Get YouTube's most-popular videos for a region (raw YouTube data). |
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 5 tools
Each tool targets a distinct resource/action: channel metadata, channel videos, outlier detection on those videos, channel search, and global trending. No two tools could be confused for one another; purposes are clearly separated.
All tool names follow a consistent verb_noun pattern: resolve_channel, get_channel_videos, find_outlier_videos, search_channels, get_trending. The verbs are specific and the nouns are descriptive, making the pattern predictable and easy to scan.
Five tools is well within the ideal 3–15 range and aligns nicely with the server's focused purpose (YouTube outlier detection). Each tool covers a necessary step without redundancy or bloat.
The core workflow is covered: resolve a channel, list its videos, detect outliers, and optionally search channels or check trending. Minor gaps exist (e.g., no way to manually define outlier thresholds or fetch video-level comments), but these don't break the primary use case.