Skip to main content
Glama

Google Videos Generate

google-videos-generate
Read-only

Generate videos from text prompts or reference images/videos using Google Veo. Optionally wait for completion and download the generated videos.

Instructions

Generate videos using Google GenAI (Veo). Can optionally wait for completion and download generated videos to MEDIA_GEN_DIRS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptNoText prompt that describes the video to generate (max 32K chars). Required unless an input image/video is provided.
input_referenceNoOptional image reference (image-to-video): HTTP(S) URL, base64 / data URL, or file path under MEDIA_GEN_DIRS.
input_reference_mime_typeNoOptional override for input image MIME type (e.g. image/jpeg). Useful when input_reference is raw base64 without a data URL header.
input_video_referenceNoOptional input video reference (video extension): HTTP(S) URL or file path under MEDIA_GEN_DIRS. Mutually exclusive with input_reference.
modelNoGoogle video model id (default: veo-3.1-generate-001).veo-3.1-generate-001
number_of_videosNoNumber of videos to generate (default: 1).
aspect_ratioNoAspect ratio for the generated video.
duration_secondsNoVideo duration in seconds (provider/model-dependent).
person_generationNoControls whether people are allowed in the generated video.
wait_for_completionNoIf true, poll the operation until done (then optionally download). Default: true.
timeout_msNoMax time to wait for completion when wait_for_completion is true (default: 900000).
poll_interval_msNoPolling interval when wait_for_completion is true (default: 10000).
download_when_doneNoWhen waiting, whether to download generated videos to MEDIA_GEN_DIRS[0]. Defaults to true when wait_for_completion=true, otherwise false.
tool_resultNoControls content[] shape when downloading: 'resource_link' (default) emits ResourceLink items, 'resource' emits EmbeddedResource blocks with base64 blob.resource_link
response_formatNoControls structuredContent video fields: 'url' (default) prefers video.uri, 'b64_json' prefers video.videoBytes.url
Behavior1/5

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

The description claims to generate videos (a write operation), but the annotation says readOnlyHint=true. This is a direct contradiction. Additionally, no information about destruction, authentication, or rate limits is provided.

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 very concise (two sentences) and front-loaded with purpose. However, it lacks structure (e.g., sections) but is efficient for a simple tool.

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

Completeness2/5

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

Given 15 parameters and no output schema, the description is too brief. It does not explain common use cases (e.g., image-to-video, video extension), return value shape, or when to use different parameter combinations. The schema covers details, but description should summarize.

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

Parameters3/5

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

Schema coverage is 100% with detailed parameter descriptions. The description adds no parameter-level information beyond 'Can optionally wait for completion and download...' which is already implied by parameters. Baseline 3 is appropriate.

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 it generates videos using Google GenAI (Veo) and mentions optional waiting and downloading. This distinguishes it from sibling tools like OpenAI video generation and retrieval tools.

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?

The description implies when to use (generate a video) but does not provide explicit guidance on when not to use or alternatives. It mentions optional waiting and downloading, but no context on trade-offs or prerequisites.

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/strato-space/media-gen-mcp'

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