Skip to main content
Glama

Text To Video

text_to_video

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


Available models:

  • Ltx2_5_22B_Dist_INT8: size=512-1344x512-1344, fps=24 (fixed), frames=49-241, w/h rounded down to a multiple of 64, ≤1.03Mpx, side≤1344, aspect≤2, audio2video audio=1-10s, no negative_prompt

  • MiniMaxH3_33B_Turbo_INT8: size=512-1344x512-1344, fps=24 (fixed), frames=56-243, w/h rounded down to a multiple of 32, ≤1.03Mpx, side≤1344, refs: ≤3 images, ≤1 video (0.5-2.3s), ≤3 audio (1-10s), ≤3 files total, no negative_prompt

  • Ltx2_3_22B_Dist_INT8: size=512-1024x512-1024, fps=24 (fixed), frames=49-241, audio2video audio=1-11s, no negative_prompt

  • Ltxv_13B_0_9_8_Distilled_FP8: steps=1 (fixed), size=256-768x256-768, fps=30 (fixed), frames=30-120

  • veo-3.1 (test model): steps=1 (fixed), size=720-1920x720-1920, fps=24 (fixed), frames=97-193, w/h rounded down to a multiple of 8, ≤2.07Mpx, side≤1920, aspect≤1.78, no negative_prompt

  • veo-3.1-fast (test model): steps=1 (fixed), size=720-1920x720-1920, fps=24 (fixed), frames=97-193, w/h rounded down to a multiple of 8, ≤2.07Mpx, side≤1920, aspect≤1.78, no negative_prompt

  • kling-4 (test model): size=720-2520x720-1920, fps=24 (fixed), frames=73-721, w/h rounded down to a multiple of 2, ≤2.72Mpx, aspect≤2.34, no negative_prompt

  • seedance-2.5 (test model): size=432-2206x432-2206, fps=24 (fixed), frames=97-721, w/h rounded down to a multiple of 2, ≤2.09Mpx, side≤2206, aspect≤2.34, refs: ≤9 images, ≤1 video (1.8-30.2s), ≤3 audio (1.8-30.2s), ≤12 files total, no negative_prompt Models marked (test model) are experimental: they may change or disappear. Prefer an unmarked model unless the caller asks for one of them.

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 observed

TDQS

A3.8/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 does add real behavioral context: experimental models 'may change or disappear', and per-model invariants such as fps=24 (fixed) or steps=1 (fixed). However, it never addresses job duration, whether generation is synchronous or long-running, rate limits, or failure modes, and cost handling is only covered for enhance_prompt in the schema rather than the description.

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?

Front-loaded with purpose and the IMPORTANT prerequisite before the long model catalogue, and the catalogue is separated with a visual divider so it can be skimmed or skipped. The first two sentences are near-duplicates ('Generate video from text prompt' / 'Creates videos from text descriptions'), which is avoidable waste, but the rest of the text is dense and earns its place.

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 a 13-parameter generation tool with an output schema, this is close to complete: it covers the mandatory prerequisite, model-specific constraints, and experimental-model risk. What is missing is operational context an agent would want before a potentially long or costly job, such as async/job-status behavior or pricing, particularly given the presence of text_to_video_price and check_job_status siblings.

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 the baseline is 3, but the description adds genuine meaning beyond the schema by enumerating each model's valid ranges for steps, fps, frames, and width/height, plus rounding rules (multiple of 64/32/8/2), megapixel caps, and aspect caps. That is information the parameter definitions alone only gesture at with 'see the model list'. It does not, however, explain prompt or seed semantics.

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?

States a specific verb and resource ('Generate video from text prompt', 'Creates videos from text descriptions') and notes the return value is a generated video URL. It implicitly separates itself from image_to_video/audio_to_video by naming the text-prompt input, but never explicitly contrasts with those siblings. Still, an agent can identify the operation without opening the schema.

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?

Explicitly prescribes a prerequisite step: 'Before calling this tool, use get_available_models()' and lists exactly which fields to inspect (limits.max_steps/min_steps, limits.max_fps/min_fps, defaults). It also advises preferring unmarked models over '(test model)' experimental ones unless the caller asks. It does not state when to choose this over image_to_video or audio_to_video, which is the remaining gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.