Skip to main content
Glama

Generate Video

generate_video

Generate a video from a text prompt. The async job saves the finished video to disk and returns its absolute path, or a polling URL if generation takes longer.

Instructions

Generate a video from a text prompt (async job: starts generation, then waits and polls). Video generation typically takes 1-5 minutes. The finished file is saved to disk and its absolute path is returned. If waiting times out, a polling_url is returned — pass it to check_video_status later instead of starting a new (billed) job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoVideo model slug, e.g. 'google/veo-3.1' or 'openai/sora-2-pro'. Omit to use the configured default.
promptYesDetailed description of the desired result. Be specific about subject, style, lighting, composition.
output_dirNoDirectory to save into (absolute, or ~ for home). Defaults to the configured output directory.
resolutionNoOutput resolution (model-dependent).
aspect_ratioNoDesired aspect ratio. Support varies by model; treated as a strong hint.
wait_secondsNoHow long to wait for completion before returning a resumable polling_url.
generate_audioNoWhether the clip should include generated audio.
filename_prefixNoShort label used in the saved filename, e.g. 'hero-banner'. Sanitized to letters, digits, dashes.
duration_secondsNoClip length in seconds (model-dependent).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoAbsolute path of the saved video, when completed
statusYescompleted | pending | in_progress | timeout | failed | error
messageNo
video_idNo
polling_urlNoPass to check_video_status to resume waiting
Behavior5/5

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

Discloses async behavior, polling, disk persistence, absolute path return, and timeout/resume pattern. Annotations indicate side effects (openWorldHint true) and non-idempotent, which the description aligns with. No contradictions.

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?

Three sentences: purpose, typical timing, and critical timeout handling. Front-loaded, no redundancy, every sentence adds unique value.

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

Completeness5/5

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

Given 9 parameters, schema coverage, and output schema involvement, the description covers the essential async workflow, timeout fallback, and output behavior. No gaps remain for agent invocation.

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 100% of parameters with descriptions. Description adds no extra parameter details beyond the timeout/polling context. Baseline 3 is appropriate since schema already does the heavy lifting.

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?

Description clearly states 'Generate a video from a text prompt' and distinguishes async nature. Explicitly mentions sibling tool check_video_status for timeout handling, differentiating from other generation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains when to use (text-to-video generation) and what to do on timeout (use polling_url with check_video_status). Warns against restarting to avoid extra billing. Lacks explicit when-not-to-use guidance but covers the key alternative.

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/legolev/mediamcp'

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