Skip to main content
Glama

grok_image_to_video

Generate an animated video from a reference image by describing the motion. Provide an image URL and optional prompt to control the animation.

Instructions

Generate AI video from a reference image using Grok Imagine.

This animates your input image into a video clip. Provide a prompt to
describe the motion you want, and optional reference images to guide style.

Use this when:
- You have a specific image you want to animate
- You want consistent visual style from a reference
- You want to turn a still photo into a short video

For video generation from text only, use grok_text_to_video instead.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoGrok Imagine model. 'grok-imagine-video' (default) supports image-to-video at a lower price. 'grok-imagine-video-1.5-preview' is image-to-video only and may offer higher fidelity.grok-imagine-video
promptNoOptional description of the motion/action to apply to the image. Examples: 'The camera slowly zooms in as the character smiles', 'Gentle wind moves the trees and clouds drift across the sky'. Optional when an image_url is provided.
durationNoVideo duration in seconds (default 8). grok-imagine-video supports 1-30; grok-imagine-video-1.5-preview supports 1-15.
image_urlYesURL of the input image to animate into a video. Required for image-to-video generation.
resolutionNoOutput resolution. '480p' (default, cheaper), '720p', or '1080p' (higher quality, costs more credits per second for grok-imagine-video-1.5-preview).480p
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.
reference_image_urlsNoOptional list of additional reference image URLs used to guide the style or content of the generated video.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It explains animation process, mentions optional callback for async behavior, and notes model differences. However, it does not explicitly disclose potential costs, rate limits, or polling necessity for result retrieval.

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

Conciseness5/5

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

Concise, well-structured with bullet points for use cases. Every sentence is informative; no redundancy. Front-loaded with the core purpose.

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

Completeness4/5

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

Covers main workflow, returns task ID and video info, mentions callback_url. For 8 parameters with 100% schema coverage and output schema, it is largely complete. Could briefly note that results require polling if no callback.

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 coverage is 100% with descriptions. The description adds value by summarizing purpose, providing prompt examples, and explaining model differences (e.g., 'grok-imagine-video-1.5-preview may offer higher fidelity'). This goes beyond raw schema.

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 a reference image. It specifically identifies the resource (image) and action (animate into video), and distinguishes from sibling grok_text_to_video by noting the alternative for text-only generation.

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?

Explicitly lists three use cases (animating specific image, consistent style, still photo to video) and directs to grok_text_to_video for text-only video generation, providing clear when-to-use and when-not-to-use guidance.

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

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