Skip to main content
Glama

veo_text_to_video

Generate AI video from a text prompt using Veo's video generation model. Describe the scene, subject, action, and style to create a matching video clip.

Instructions

Generate AI video from a text prompt using Veo.

This creates a video from scratch based on your text description. Veo
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 for Veo

For video generation starting from an image, use veo_image_to_video instead.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of the video to generate. Be descriptive about scene, subject, action, camera movement, lighting, and style. Examples: 'A white ceramic coffee mug on a glossy marble countertop, steam rising, soft morning light', 'Cinematic drone shot over a forest at sunset, golden hour lighting'
modelNoVeo model version. 'veo2' for quality mode, 'veo2-fast' for faster generation. 'veo3'/'veo31' offer improved quality. Models with '-fast' suffix are faster but slightly lower quality.veo2
aspect_ratioNoVideo aspect ratio. '16:9' for landscape/widescreen, '9:16' for portrait/vertical, '1:1' for square, '4:3' for standard, '3:4' for portrait standard.16:9
translationNoIf true, automatically translate the prompt to English for better generation quality. Useful for non-English prompts.
resolutionNoVideo resolution. Options: '4k' for highest quality, '1080p' for standard HD, 'gif' for animated GIF format. If not specified, uses the model's default resolution.
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
Behavior3/5

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

With no annotations provided, the description carries full burden. It mentions that Veo interprets the prompt and returns a task ID and video info, but does not disclose potential behavioral traits like asynchronous processing, generation time, cost, or error handling. The return info is a start but lacks depth.

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-line summary, a short paragraph, a bullet list for usage, and a returns section. Every sentence adds value with 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?

Given the tool's complexity (6 params, 1 required, output schema exists), the description adequately covers purpose, usage, and return format. It differentiates from siblings. Minor gap: no mention of error states or asynchronous workflow, but output schema likely covers details.

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 schema already documents all parameters thoroughly. The description adds no new parameter-level detail beyond the schema, meeting the baseline of 3.

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 Veo', specifying the verb and resource. It explicitly distinguishes from the sibling tool veo_image_to_video by stating the alternative use case.

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 includes a 'Use this when:' section with three clear conditions (text description, no reference image, max creative freedom) and explicitly names the alternative tool veo_image_to_video for when an image is available.

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

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