Skip to main content
Glama

generate_video

Generate or edit MP4 videos from text prompts, images, or references, with control over aspect ratio and duration.

Instructions

Generate or edit MP4 videos with Gemini Omni Flash.

Capabilities:

  • text_to_video: prompt-only video with generated audio.

  • image_to_video: one reference image plus motion and camera direction.

  • reference_to_video: multiple reference images for subjects, style, or props.

  • edit: use previous_interaction_id or input_video_path to edit existing video.

Parameters:

  • prompt: Describe the scene, motion, camera movement, lighting, mood, and audio.

  • task: text_to_video, image_to_video, reference_to_video, or edit. If omitted, inferred.

  • aspect_ratio: 16:9 landscape or 9:16 portrait.

  • duration_seconds: Optional 3 to 10 second target. If the API rejects this preview field, retry without it.

  • reference_image_paths: Up to 6 local images. Use or tags in the prompt for control.

  • input_video_path: Local MP4 to upload and edit through the Files API.

  • delivery: uri is recommended for generated MP4 files; inline is supported for smaller payloads.

  • previous_interaction_id: Continue editing a prior generated video.

  • enhance_prompt: Optional, default false. For edits, simple prompts usually work better.

Prompt tips:

  • Ask for "single continuous shot" and "no scene cuts" when you want one scene.

  • Include explicit audio direction such as "gentle ambient room tone, no dialogue".

  • For edits, say "Keep everything else the same".

  • Timing cues like [0-3s], [3-6s], [6-10s] are supported.

Limitations:

  • Output is MP4, currently 720p at 24fps, SynthID-watermarked, and preview quality.

  • System instructions, temperature, top_p, stop sequences, negative_prompt, voice edits, YouTube sources, and multi-video reasoning are unsupported.

  • Uploaded-video editing is unavailable in some regions.

Returns JSON including video.path, interaction_id, task, aspect_ratio, delivery, size, and URI metadata. After success, open video.path with the native OS video viewer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNo
promptYes
deliveryNo
aspect_ratioNo
enhance_promptNo
duration_secondsNo
input_video_pathNo
reference_image_pathsNo
previous_interaction_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses limitations (720p, 24fps, watermark, preview quality), unsupported features, region restrictions, and post-success behavior (open video.path). Annotations absent, so description carries full burden and does well.

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?

Well-structured with sections and bullets, but lengthy. Front-loads purpose. Every sentence adds value, but slight redundancy in parameter listing.

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?

Covers capabilities, parameters, prompt tips, limitations, return values. Output schema exists, but description adds detailed return structure. Complete for a complex tool with 9 parameters and a sibling.

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

Parameters5/5

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

All 9 parameters are individually described with context, defaults, and usage nuances (e.g., duration_seconds retry, reference tags). Compensates fully for 0% schema coverage.

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

Purpose4/5

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

Clearly states 'Generate or edit MP4 videos' and enumerates four specific capabilities (text_to_video, etc.). Distinguishes from sibling 'batch_generate' by focusing on single generation/editing tasks, though not explicitly contrasted.

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

Usage Guidelines3/5

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

Provides task categories and prompt tips, but lacks explicit guidance on when to use vs. batch_generate or when to avoid. Usage context is implied rather than stated.

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/nikships/gemini-omni-mcp'

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