Skip to main content
Glama
mnthe

gemini-mcp-server

by mnthe
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

generate_omni_video

Generate short videos from text or images, or edit existing videos with natural language instructions, using Gemini Omni Flash. Returns video synchronously without polling.

Instructions

Generate or conversationally edit short videos with Gemini Omni Flash (gemini-omni-flash-preview). This is a NON-Veo model on the Google AI Studio (Gemini API) backend and does NOT use generate_video/check_video: it returns the finished video synchronously in one call (no operationId polling). Two paths: (1) ONESHOT generation — text-to-video, or image/reference-to-video via imagePaths (max 7); (2) INTERACTIVE editing — set previousInteractionId to an id returned by a prior call to edit that video with a natural-language instruction (no image re-upload; chain up to 3 sequential edits). Constraints: 720p output only; aspect ratio 16:9 or 9:16; clips run a few seconds (steer pacing/timing within the prompt — duration is not a parameter); a synced audio track is generated automatically (audio reference inputs are not accepted — describe dialogue/SFX/ambience in the prompt). Image source file types: PNG (.png), JPEG (.jpg/.jpeg), WEBP (.webp). The response includes interactionId (pass it back as previousInteractionId to edit) and the saved file path. Videos are saved to /root/Videos/gemini-generated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoOmni video model (default: gemini-omni-flash-preview)
promptYesVideo prompt for a new generation (oneshot), or a natural-language edit instruction when previousInteractionId is set (interactive editing). Describe dialogue/SFX/ambience as text; audio reference files are not accepted.
imagePathsNoLocal file paths of source/reference images for image-to-video or reference-to-video (max 7). Supported file types: PNG (.png), JPEG (.jpg/.jpeg), WEBP (.webp). Omit for interactive edits — previousInteractionId reuses the prior video.
aspectRatioNoAspect ratio (default: 16:9). Omni Flash supports 16:9 and 9:16 only. Output is 720p only.
previousInteractionIdNoInteraction ID from a prior generate_omni_video call. When set, conversationally edits that video (no image re-upload) instead of generating a new one.

Tool Definition Quality

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses key behaviors: synchronous execution (no polling), 720p output, auto-generated audio, no audio input, supported image types, and response fields (interactionId, file path). No contradictions exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-organized, front-loading the core purpose and then detailing paths, constraints, and response. While slightly verbose, every sentence adds value. Minor conciseness improvements could be made.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description explains the response format (interactionId, saved file path). It covers all necessary aspects: model, modes, inputs, constraints, process, and output. It also differentiates from sibling tools effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds meaningful context beyond the schema, such as the dual role of prompt (oneshot vs. edit), the omission of imagePaths for edits, and the 720p constraint for aspectRatio.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates or conversationally edits short videos using Gemini Omni Flash, distinguishing it from sibling tools like generate_video (which uses a different model and polling). It specifies two distinct paths (oneshot and interactive editing) and lists key capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is provided on when to use each path: oneshot for new video (text-to-video or with images) and interactive editing by setting previousInteractionId. Constraints like max 7 images, no audio references, and supported aspect ratios are clearly stated, and it implicitly distinguishes from sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mnthe/gemini-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server