Skip to main content
Glama
AceDataCloud

GrokMCP

by AceDataCloud
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

grok_image_to_video

Generate an AI video from a still image by supplying an image URL and optional motion prompt. Set duration, resolution, and aspect ratio to create a short animated clip.

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. All models support image-to-video. 'grok-imagine-video-1.5-fast:reverse' (default) is fastest and cheapest; 'grok-imagine-video-1.5:official' offers the highest fidelity (up to 1080p) and is image-to-video only; 'grok-imagine-video' provides standard quality image-to-video generation.grok-imagine-video-1.5-fast:reverse
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 6). 'grok-imagine-video-1.5-fast:reverse' supports 6-30; every other model 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 resolution costs more per second on the per-second-priced models.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

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the operation (animating image into video) and the return shape (Task ID, video information, URLs, state). However, it does not explicitly state that generation is asynchronous, whether the response is immediate or requires polling via grok_get_task, or any limitations on input images. This ambiguity is a notable gap.

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?

The description is concise and well-structured: a one-sentence purpose, a brief explanation, a bulleted 'Use this when' list, a sibling-tool pointer, and a return summary. Every sentence earns its place; no fluff.

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?

For an 8-parameter tool with a rich schema and output schema, the description covers purpose, usage, and returns. The main gap is the lack of explicit guidance on the async task lifecycle (e.g., 'returns a task ID immediately; use grok_get_task to poll for completion'). Given the sibling tools include grok_get_task, this context would complete the picture.

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%, so the baseline is 3. The description adds only minimal context beyond the schema, such as mentioning prompt for motion and reference images for style. It does not explain parameter interactions or constraints beyond what the schema already provides.

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 starts with a specific verb+resource: 'Generate AI video from a reference image using Grok Imagine.' It clearly states the tool animates an input image into a video clip. It distinguishes itself from the sibling tool grok_text_to_video by explicitly directing text-only generation there.

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?

The description provides a 'Use this when' bullet list with three concrete scenarios, and directly names the alternative tool ('For video generation from text only, use grok_text_to_video instead'). This gives 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