Viral Shorts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUTUBE_API_KEY | Yes | Your YouTube Data API v3 Key. Can be obtained from the Google Cloud Console with YouTube Data API v3 enabled. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_youtube_shorts_trendsC | 发现 YouTube Shorts 上的潜在热门视频。通过分析播放量、互动率和发布时间,识别高质量的短视频。 |
| analyze_video_potentialC | 深度分析单个 YouTube Shorts 视频的表现。提供详细的播放量、互动率等核心指标。 |
| get_trending_topicsC | 发现当前 YouTube Shorts 上的热门话题和趋势。分析多个分类的热门内容,帮助选题。 |
| summarize_video_storyC | 提炼 YouTube Shorts 视频的故事梗概和核心内容。基于视频标题和描述,分析视频的主题、情节和创作手法。 |
| discover_niche_trendsC | 智能发现某个主题下的细分爆款领域。通过分析大量视频标题,自动识别高 VPH 的关键词组合,例如在 'AI' 主题下发现 'AI Kpop'、'AI 印度故事' 等细分趋势。 |
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
Multiple tools have unclear boundaries and overlapping purposes. 'get_trending_topics' and 'get_youtube_shorts_trends' both focus on discovering trends/hot content with similar descriptions, while 'analyze_video_potential' and 'summarize_video_story' both analyze individual videos but with different aspects (performance metrics vs. content/story). This overlap could cause agent misselection confusion.
The naming is mostly consistent with a clear verb_noun pattern (e.g., analyze_video_potential, discover_niche_trends). All tools use snake_case and descriptive names, with only minor deviations like 'get_youtube_shorts_trends' being slightly redundant compared to 'get_trending_topics'.
With 5 tools, the count is well-scoped and appropriate for the server's purpose of YouTube Shorts analysis. Each tool appears to serve a distinct function within the domain, and the number is manageable without being too thin or overwhelming.
The tool surface covers analysis, trend discovery, and summarization for YouTube Shorts, but there are notable gaps. It lacks CRUD/lifecycle operations (e.g., no tools for creating, updating, or managing content), and the focus is primarily on reading/analyzing existing data, which may limit agent workflows for content creation or optimization.