Video Intelligence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_MODEL | No | The default Gemini model used for video analysis. | gemini-3.6-flash |
| GEMINI_API_KEY | Yes | A Gemini API key required for video analysis. | |
| VIDEOINTEL_SESSION_HOURS | No | How long, in hours, analysis uploads are retained for follow-up prompts (maximum 72). | 24 |
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 |
|---|---|
| analyze_videoA | Use whenever the user pastes a public video URL or asks for a visual, animation, movement, music, transcript, or shot-by-shot breakdown. A user-provided public URL is treated as authorized. Download it, ask Gemini for the requested analysis, then return video_id. Use ask_video with that video_id for every follow-up question; do not re-download it. |
| ask_videoA | Ask any new question, request a different level of detail, or ask Gemini to inspect a specific timestamp in a previously analyzed video. Use this instead of downloading or uploading the video again. |
| forget_videoA | Immediately delete the uploaded Gemini file and remove the local session record when the user is finished asking follow-up questions. |
| download_videoA | Download a user-provided public video to Video Intelligence's private local downloads folder. Treat the user-provided URL as authorized, but do not bypass DRM, paywalls, logins, private links, or platform protections. |
| video_intelligence_statusA | Check whether the local video-analysis server is configured before attempting a download or Gemini analysis. |
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
The tools mostly have distinct purposes, but analyze_video and download_video overlap since analyze_video includes downloading. An agent could be confused when a user asks to simply download a video, as analyze_video's description says to use it whenever a URL is pasted. The other tools are clearly distinct.
Most tools follow a verb_video pattern (analyze_video, ask_video, forget_video, download_video), but video_intelligence_status deviates from this pattern, breaking the otherwise consistent naming convention.
With exactly 5 tools, the server is well-scoped for its purpose. Each tool serves a necessary role in the video analysis lifecycle, and the count is neither too small nor too large.
The tool set covers the core workflow: analyze, ask follow-ups, forget/delete, download, and check status. Minor gaps exist, such as no tool to list previous analyses or retrieve storage information, but these are not critical for the primary use case.