youtube-gemini-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR, default: INFO) | |
| GOOGLE_API_KEY | Yes | Your Google AI API key (required) | |
| MCP_MAX_SESSIONS | No | Maximum concurrent sessions (default: 50) | |
| AUTO_CLEANUP_FILES | No | Auto-cleanup uploaded files (default: true) | |
| MAX_VIDEO_DURATION | No | Maximum video length in seconds (default: 7200) | |
| MCP_SESSION_TIMEOUT | No | Session timeout in seconds (default: 7200) | |
| GEMINI_MODEL_DEFAULT | No | Default Gemini model (default: gemini-2.5-pro-preview-05-06) |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_video_sessionB | Create new conversational video analysis session. Args: description: Session context/purpose video_source: YouTube URL or local video file path model: Gemini model to use session_name: Optional friendly name source_type: "youtube_url" (default) or "local_file" |
| analyze_video_in_sessionB | Analyze video within session context. Args: session_id: UUID of existing session prompt: Analysis question/instruction timestamp_range: Optional "MM:SS-MM:SS" for segment analysis |
| analyze_youtube_videoA | Single-shot or session-integrated YouTube video analysis using direct URL method. Args: youtube_url: YouTube video URL or ID prompt: Analysis instruction model: Gemini model to use session_id: Optional session for context |
| analyze_local_videoA | Single-shot or session-integrated local video analysis using Files API. Args: video_path: Local video file path prompt: Analysis instruction model: Gemini model to use session_id: Optional session for context |
| get_session_statusC | Get current session status and history. |
| list_active_sessionsB | List all active video analysis sessions. |
| close_sessionC | Close session and cleanup resources. |
| validate_youtube_urlB | Validate and normalize YouTube URLs/IDs. |
| get_usage_guideB | Comprehensive tool documentation and examples. |
| get_server_statsA | Server statistics and health monitoring. |
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 10 tools
The three analysis tools (analyze_local_video, analyze_video_in_session, analyze_youtube_video) have overlapping purposes, as the first and third can also work with sessions. Although descriptions clarify differences, an agent might struggle to select the correct tool without careful reading.
All tool names follow a consistent verb_noun pattern in snake_case, such as 'analyze_local_video', 'create_video_session', and 'list_active_sessions'. No mixing of conventions or irregular names.
The server has 10 tools, which is well-scoped for its domain of video analysis and session management. Each tool serves a distinct purpose without unnecessary clutter.
The tool set covers core workflows: creating sessions, analyzing videos (local or YouTube), managing sessions, and utilities (validation, stats, guide). Minor gaps like lacking explicit update for sessions are mitigated by session lifecycle tools.