yt-analytics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YT_ANALYTICS_DATA | No | Directory path for caching analyses and transcripts. Defaults to 'data/' inside the project. |
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 |
|---|---|
| yt_analyze_channelA | Analyze a YouTube channel: download transcripts and compute quantitative metrics (WPM, profanity, humor taxonomy, rhetoric fingerprint, title formula). Returns structured JSON. Results are cached for use in comparisons. |
| yt_list_analysesA | List all cached channel analyses. Returns channel names, video counts, and analysis dates. |
| yt_get_analysisB | Retrieve the full cached analysis JSON for a specific channel. |
| yt_remove_analysisB | Remove a cached channel analysis. |
| yt_compare_creatorsA | Build or update a tabbed HTML comparison dashboard from cached analyses. Specify which channels to include, or omit to include all cached analyses. Returns the HTML file 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 5 tools
Each tool has a clearly distinct purpose: analyzing a channel, comparing creators, retrieving cached analyses, listing them, and removing them. No overlap exists.
All tools follow a consistent 'yt_verb_noun' pattern (e.g., yt_analyze_channel, yt_compare_creators), making the naming predictable and uniform.
With 5 tools, the server is well-scoped for managing YouTube channel analyses. The count is appropriate for the domain without being excessive or insufficient.
The tool set covers the full lifecycle: create analysis, retrieve (list/get), update (compare dashboard), and delete. No obvious gaps for the intended purpose.