Skip to main content
Glama

veo_image_to_video

Generate AI video from reference images by describing desired motion. Supports first-frame animation from one image, interpolation between 2-3 images, and multi-image fusion for consistent style.

Instructions

Generate AI video from one or more reference images using Veo.

This creates a video using your image(s) as reference frames. The video
will animate from/between your provided images according to the prompt.

Image modes:
- 1 image: First-frame mode - the video starts from your image
- 2-3 images: First-last frame mode - video interpolates between images
- veo31-fast-ingredients model: Multi-image fusion - blends elements from all images

Use this when:
- You have a specific image you want to animate
- You want consistent visual style from a reference
- You need to create a video transition between two images

For video generation from text only, use veo_text_to_video instead.

Returns:
    Task ID and generated video information including URLs and state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoVeo model version. Note: 'veo31-fast-ingredients' is for multi-image fusion mode only. Other models support 1 image (first frame) or 2-3 images (first/last frame).veo31-fast
promptYesDescription of the video motion and action. Describe what should happen to the subject in the image. Examples: 'The coffee steam rises gently', 'The person turns and smiles at the camera', 'Camera slowly zooms out revealing the landscape'
image_urlsYesList of image URLs to use as reference. For first-frame mode, provide 1 image. For first-last frame mode, provide 2-3 images. The first image is the starting frame, the last image is the ending frame. Maximum 3 images.
resolutionNoVideo resolution. Options: '4k' for highest quality, '1080p' for standard HD, 'gif' for animated GIF format.
translationNoIf true, automatically translate the prompt to English for better generation quality.
aspect_ratioNoVideo aspect ratio. Should typically match your input image aspect ratio for best results.16:9
callback_urlNoOptional URL to receive a POST callback when generation completes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any side effects, costs, rate limits, or asynchronous behavior beyond vague mention of returning a task ID. It lacks transparency about operational implications.

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

Conciseness2/5

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

The description is verbose, redundantly repeating schema details in narrative form. Although structured with sections, it could be much more concise without losing information.

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

Completeness3/5

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

Given the schema's richness, the description covers purpose, usage, and return values adequately. However, it omits potential error scenarios, limitations, or additional operational context, making it only moderately complete.

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 covers all parameters with descriptions, achieving 100% coverage. The description adds minimal new meaning—it repeats schema info but does not clarify undefined aspects. Baseline of 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 the tool generates AI video from reference images and explicitly distinguishes it from text-to-video by mentioning the alternative veo_text_to_video. The purpose is unambiguous.

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?

Provides explicit 'Use this when' conditions and contrasts with text-only generation. Clearly guides when to choose this tool over alternatives.

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

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/AceDataCloud/VeoMCP'

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