Skip to main content
Glama

fitv-mcp

Generate a video on Free Image to Video

generate_video

Generate a video clip with sound from a text prompt on freeimagetovideo.ai, or animate a photo by passing image_url (photo to video). Defaults to MiniMax H3 at 480p. Needs a paid plan: each run draws on the plan's daily full-speed allowance, then waits in the relaxed queue (https://freeimagetovideo.ai/pricing). Video takes minutes: this returns a run id to poll with check_status.

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>"
    },
    "name": "generate_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNominimax-h3 (MiniMax H3), the model this site runs.
promptYesThe shot: what happens, where, how the camera moves, and what it sounds like.
durationNoSeconds: 4/5/6/8/10/15.
image_urlNoOptional photo (public https URL) used as the first frame — makes this photo to video.
resolutionNo'480p' or '768p'.
aspect_ratioNo'16:9' (default), '9:16' or '1:1'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare mutating, open-world, non-destructive behavior, so the bar is lower. The description still adds real value beyond them: paid-plan gating, the full-speed-then-relaxed-queue consumption model with a pricing link, and the crucial async contract (minutes-long runtime, returns a run id to poll). It omits any statement about content limits, failure/refund behavior, or whether assets persist.

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 capability and modes, then defaults, then the plan/queue constraint, then the async return contract — a sensible order with no filler sentences. Slightly dense, with the domain URL appearing twice, but nothing that could be cut 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?

For a six-parameter mutation with no output schema, the description covers the essentials an agent needs before calling: prerequisites, latency, and how to retrieve results via check_status. Only the actual return payload shape (beyond 'a run id') and cost-per-run are left unaddressed.

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 description coverage is 100%, so parameter meaning is largely carried by the schema and a 3 baseline applies. The description does add two things beyond the schema: the default of MiniMax H3 at 480p, and the framing of image_url as 'first frame' producing photo-to-video, which clarifies how the optional param changes the operation.

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?

States a specific verb and resource ('Generate a video clip with sound from a text prompt') and immediately names the second mode ('animate a photo by passing image_url'). An agent can distinguish text-to-video from photo-to-video and knows the terminal sibling is check_status without opening a 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?

Gives clear operating context: requires a paid plan, draws on a daily full-speed allowance then falls back to a relaxed queue, and hands off to check_status for polling. It doesn't state explicit when-not-to-use conditions or cost per run (a sibling 'credits' tool is implied but never referenced), so it falls short of a full routing rule.

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.