Skip to main content
Glama
qmediat

ideogram-mcp

by qmediat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Video from an image

ideogram_video_image

Animate a still image into an MP4 video from a text prompt, optionally ending on a second image, using Seedance, Kling, or MiniMax models.

Instructions

A video that starts from an image (and optionally ends on another): Seedance 2.5 by default, Seedance 2, Kling 3 Standard, MiniMax H3. Takes local files, public https URLs or Ideogram assets. Saved as mp4; long jobs come back as a generation_id. ideogram_quote prices a call first.

Input Schema

NameRequiredDescriptionDefault
imageNoLocal image file (or public https URL) the video starts from; not with image_asset_identifier
modelNoThe model (default seedance-2-5-image-to-video); each takes the fields of its variant below
promptNoWhat the video shows, in natural language
wait_sNoSeconds to wait for the result (0-50, default 45). The job is accepted first; if it is still running when the wait ends, the result is its generation_id for ideogram_generation (never resubmitted, never billed twice).
privateNoKeep the result out of Ideogram's public feed; true unless you set false (enterprise accounts are always private)
durationNoLength of the video in seconds (Seedance 2.5: 4-30, Seedance 2: 4-15, Kling: 3-15, MiniMax: 5-15). Omitted: Kling and MiniMax make 5 s; Seedance picks the length for the prompt and is QUOTED at its maximum length (30 s on 2.5, 15 s on 2) — give it, and ideogram_quote tells the price
cfg_scaleNoHow closely the video follows the prompt, 0-1 (default 0.5); lower leaves the model more freedom
end_imageNoLocal image file (or public https URL) the video ends on; not with end_image_asset_identifier
shot_typeNoHow the prompt is staged: customize follows it as written, intelligent lets the model split it into its own shots
resolutionNoThe resolution tier: 480p, 720p (default) or 1080p on Seedance 2.5 (480p/720p on Seedance 2), 480P, 768P, 2K (default) or 4K on MiniMax (2K and 4K are upscaled from 768P); higher costs more
aspect_ratioNoThe video's aspect ratio such as 16x9 (auto on Seedance lets the model choose from the prompt); with resolution where the model takes both
generate_audioNoAlso generate an audio track (about double the price per Ideogram — the dry-run quote does not include it; stricter moderation)
negative_promptNoWhat to keep out of the video
image_asset_identifierNoAn Ideogram asset the video starts from; not with image
end_image_asset_identifierNoAn Ideogram asset the video ends on; not with end_image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.0

TDQS

A3.5/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, and it does disclose the output medium (saved as mp4) and the async fallback (long jobs return a generation_id). However, it omits the wait_s polling/accept-then-resume behavior and the private-by-default posture, both of which live only in the schema.

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?

Three compact sentences, front-loaded with the core purpose, then inputs, then output/pricing. Little waste, though the model list and pricing pointer make it slightly dense.

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 15-parameter, four-variant tool with no output schema, the description covers source types, model choices, output format, and pricing hand-off, leaving only polling semantics to the schema. Completeness is solid, if not exhaustive.

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 the schema already documents all 15 parameters, setting the baseline at 3. The description adds only the model roster and the accepted input source types (local files, https URLs, Ideogram assets), which the schema largely mirrors.

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+resource ('A video that starts from an image') and enumerates the four supported models, which cleanly separates it from ideogram_video_text (text-driven) and ideogram_video_reference. It does not explicitly name those siblings, so it stops short of a 5.

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?

Gives implied context (image-to-video, optional end image) and routes the agent to ideogram_quote for pricing, but offers no explicit when-to-use-vs-alternatives guidance against the other two video tools or the image-editing siblings.

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

Deploy Server

Other Tools