Skip to main content
Glama

grok_text_to_video

Generate a video from a text prompt. Describe the scene, action, and style to produce a custom AI video.

Instructions

Generate AI video from a text prompt using Grok Imagine.

This creates a video from scratch based on your text description. Grok
Imagine will interpret your prompt and generate a matching video clip.

Use this when:
- You want to create a video from a text description
- You don't have a reference image to use
- You want maximum creative freedom

Only the 'grok-imagine-video' model supports text-to-video. For generating
a video from a reference image, use grok_image_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 both text-to-video and image-to-video at a lower price. 'grok-imagine-video-1.5-preview' supports image-to-video ONLY and requires an image_url — do not use it here for text-to-video.grok-imagine-video
promptYesDescription of the video to generate. Be descriptive about scene, subject, action, camera movement, lighting, and style. Examples: 'A cinematic shot of a kitten chasing a butterfly in a sunlit garden', 'Drone shot flying over a neon-lit cyberpunk city at night'. Required for text-to-video with the 'grok-imagine-video' model.
durationNoVideo duration in seconds (default 8). grok-imagine-video supports 1-30; grok-imagine-video-1.5-preview supports 1-15.
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. '16:9' for landscape/widescreen, '9:16' for portrait/vertical, '1:1' for square, plus '4:3', '3:4', '3:2', '2:3'.16:9
callback_urlNoOptional URL to receive a POST callback when generation completes. The callback will include the task_id and video results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It explains that the tool creates a video from scratch based on description and returns task ID and video info. Though it could be more explicit about async behavior, it adequately discloses the core behavior.

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 front-loaded with the main purpose, uses bullet points for clarity, and keeps sentences efficient. It could be slightly more compact, but it is well-structured and avoids unnecessary words.

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?

Given the complexity (6 parameters, output schema exists), the description covers purpose, usage, and return information. It omits error handling and rate limits, but for a generation tool this is sufficient. Output schema covers return values, so no need to elaborate.

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 description coverage is 100%, so baseline is 3. The description does not add additional meaning beyond the schema for individual parameters; it only provides general context. Thus score remains at baseline.

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 'Generate AI video from a text prompt using Grok Imagine', specifying the verb (generate), resource (AI video), and source (text prompt). It explicitly distinguishes from the sibling tool grok_image_to_video by stating when to use each.

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 explicit 'Use this when:' bullets and notes that only 'grok-imagine-video' supports text-to-video, directing users to the correct tool for image-to-video. This gives clear guidance on when to use this tool versus alternatives.

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