Skip to main content
Glama

Text To Video Price

text_to_video_price

Calculate price for text-to-video generation.


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": {
      "model": "<model>"
    },
    "name": "text_to_video_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoFrames per second (optional; limits per model, see the model list)
modelYesVideo generation model name
stepsNoNumber of inference steps. Limits per model (see the model list)
widthNoVideo width in pixels. Limits per model (see the model list)
framesNoNumber of video frames. Limits per model (see the model list)
heightNoVideo height in pixels. Limits per model (see the model list)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose substantial behavior: per-model fixed fps/steps, coordinate rounding rules, megapixel and aspect caps, and the warning that test models are experimental and may change or disappear. It omits what the returned price represents (currency, per-generation vs per-second) and does not state that the tool has no side effects.

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 purpose sentence is front-loaded and the per-model bullet list is dense with unique constraints rather than filler. It is long by necessity, though the repeated boilerplate ("no negative_prompt", "24 (fixed)") could be factored out to shorten it without losing information.

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?

An output schema exists, so return-value detail is rightly omitted, and the description covers the complex part of the call: model-specific valid ranges for fps, steps, frames, width and height. The remaining gap is the undocumented refs parameters and the absence of any statement about what the computed price means or its units.

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 schema only defers with "limits per model (see the model list)" while the description actually supplies those limits per model, which is real added meaning. One gap: it documents ref-image/video/audio limits for some models even though the input schema exposes no ref parameters, which may mislead an agent into looking for them.

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?

"Calculate price for text-to-video generation" gives a specific verb (calculate) and resource (text-to-video price), which cleanly separates it from the sibling text_to_video generator. It never states the negative case explicitly ("does not render video, use text_to_video for that"), so differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

The description gives one genuine usage rule, but it is about model selection ("Prefer an unmarked model unless the caller asks for one of them"), not about when to call this tool instead of text_to_video or the other *_price siblings. There is no statement of when a caller should price-check versus generate, or whether this must be called before generation.

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.