Skip to main content
Glama

Text To Video

text_to_video

Generates a video from a text prompt and returns the video URL. Set model, resolution, frames, and steps to control output, and use get_available_models first to check each model's limits.

Instructions

Generate video from text prompt.

Creates videos from text descriptions. Returns the generated video URL.

IMPORTANT: Before calling this tool, use get_available_models() to check the model's specifications. Pay special attention to:

  • limits.max_steps/min_steps: Valid range for steps parameter

  • limits.max_fps/min_fps: Valid range for fps parameter

  • defaults: Recommended values for the model

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>",
      "model": "<model>"
    },
    "name": "text_to_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoFrames per second. Defaults to the model's own value (see the model list); most models fix it
seedNoRandom seed for reproducibility
modelYesVideo generation model name
stepsNoNumber of inference steps. Defaults to the model's own value (see the model list); ignored by models that do not support steps
widthNoVideo width in pixels. Defaults to the model's own value (see the model list)
framesNoNumber of video frames. Defaults to the model's own value (see the model list); each model has its own range
heightNoVideo height in pixels. Defaults to the model's own value (see the model list)
promptYesText prompt for video generation
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
enhance_promptNoLet the API rewrite the prompt before generating. Only on models with a prompt-booster guide (422 otherwise); its fee is charged on the job and is not in the /price quote
guidance_scaleNoGuidance scale. Leave unset to use the model's own default; no model in the catalogue currently supports guidance
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript
negative_promptNoThings to exclude (optional)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A3.9/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 behavioral burden. It discloses that the tool returns a generated video URL and warns that steps/fps must fall within model-declared ranges, but says nothing about cost, job duration, asynchronous polling via check_job_status, or failure modes.

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 core purpose and return value are front-loaded in two short sentences, followed by a clearly bulleted prerequisite. The opening two sentences are near-duplicates ('Generate video from text prompt' vs 'Creates videos from text descriptions'), a minor redundancy.

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?

An output schema exists, so return values need no elaboration, and the rich per-parameter schema descriptions already explain defaults and webhook semantics. The description fills the remaining gap—model-specific parameter ranges—by routing to get_available_models, making it complete for a 13-parameter generation tool.

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%, so baseline would be 3, but the description adds real value by telling the agent where authoritative bounds live (limits.max_steps/min_steps, max_fps/min_fps, defaults via get_available_models) rather than letting the agent guess sensible values for the 13 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Generate video from text prompt', 'Creates videos from text descriptions') and names the return value. The 'text' input modality implicitly distinguishes it from image_to_video and audio_to_video siblings, but no sibling is named explicitly.

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?

It gives an explicit, actionable prerequisite: call get_available_models() before this tool and inspect limits and defaults for steps, fps, and the model itself. It stops short of stating when to prefer alternatives (e.g., the paired text_to_video_price or other modality tools) or any when-not-to-use condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.