Skip to main content
Glama

Image To Video Price

image_to_video_price

Calculate price for image-to-video generation.

For reference mode, pass the number of reference files the job will carry (not the files themselves). Surcharges do not stack: the highest applies, so 4 images plus a video is x3, not x6.


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

  • 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": "image_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)
ref_audios_countNoHow many ref_audios the job will send. No surcharge
ref_images_countNoHow many ref_images the job will send. More than 2 doubles the price
ref_videos_countNoHow many ref_videos the job will send. Any video triples the price

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 behavioral burden, and it does add real substance: surcharges do not stack ('4 images plus a video is x3, not x6') and test models may change or disappear. It still omits price units, whether the quote is per-request or per-second, and any rate-limit or auth context, leaving meaningful behavioral gaps for a no-annotation tool.

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, then the reference-mode caveat, then the model table — a sensible order. The model enumeration is long, but each entry carries distinct constraints, so the length is largely functional rather than padding.

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?

With nine parameters, no annotations, and per-model constraints, the description does the heavy lifting well — pricing rules, model limits, experimental-model caveats, and reference-count semantics are all present. The output schema covers the return value, but price units/semantics and the relationship to image_to_video are still unstated.

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 is the per-model 'model list' the schema explicitly defers to — supplying size/fps/frames/steps limits per model and rounding rules. It also clarifies cross-parameter interaction that no single schema field states: ref_images/ref_videos surcharges combine by taking the maximum, and ref_audios never surcharge.

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 opening line gives a specific verb and resource ('Calculate price for image-to-video generation'), which cleanly separates it from generation siblings like image_to_video and from the other *_price tools. It stops short of explicitly naming the generation counterpart, so an agent must infer the price-vs-execute distinction from the verb alone.

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 concrete caller guidance: pass reference counts rather than files in reference mode, and prefer unmarked models over '(test model)' ones unless requested. Missing is any explicit statement of when a caller should call this instead of image_to_video, or whether a price quote is required before generating.

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.