Skip to main content
Glama

animate_pixminimax

Animate a static frame into a fluid clip from a text motion description. Generate 4-40 frames with optional keyframe interpolation for longer animations.

Instructions

Beta (tier 1+ subscription): animate a single frame from a text description of the MOTION using the PixMiniMax engine (MiniMax H3). Best for fluid, longer clips — 4 to 40 frames (multiples of 4) at up to 256x256. Result holds frame_count + 1 images: index 0 is your unchanged input frame. Optional last_frame makes it a keyframe interpolation. Priced by clip length and size (about 1-12 generations); sizes just above 64 or 128px are cheaper than just below. Typically takes 1-5 minutes. Use animate_with_text_v3 for the standard engine.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoSeed for reproducible generation (0 = random, default 0)
directionNoFacing direction of the sprite (south = towards camera). Only used with enhance_prompt to hold the facing and aim attacks that way. Omit to let the enhancer read it from the image
last_frameNoOptional end pose, same size as first_frame — the motion is generated between the two
descriptionYesThe motion to generate (e.g. 'walking forward', 'sword slash', 'flame flickering'). Describe movement, not appearance. Max 1000 chars
first_frameYesStarting frame (max 256x256)
frame_countNoFrames to generate — a multiple of 4 from 4 to 40 (default 8)
no_backgroundNoReturn frames on transparency; an opaque input is cut out of its first frame before animating (default true)
enhance_promptNoExpand description into a detailed PixMiniMax motion prompt before generating (+0.05 generations; expanded text returned as enhanced_prompt). Default false
drift_thresholdNoColor de-flicker sensitivity. Frames whose foreground drifts from the first frame beyond this are corrected toward it; 0 corrects every frame, higher corrects fewer. Omit for the default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and delivers: output count (frame_count + 1), unchanged first frame, optional last_frame interpolation, pricing model, expected latency (1-5 minutes), no_background behavior, enhance_prompt effect, and drift_threshold de-flicker behavior. No contradiction with any structured data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence adds essential operational or selection information. It front-loads the core purpose and alternative, then details constraints, pricing, and behavior without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, nested-object tool with no output schema, the description covers return shape, timing, pricing, constraints, and engine differentiation. It explains side effects (unchanged first frame, background removal, enhanced prompt) sufficiently for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the description adds significant meaning beyond field titles: frame_count must be a multiple of 4 and affects cost, result includes an extra frame, last_frame implies keyframe interpolation, and dimensions affect pricing (sizes just above 64/128px cheaper). This materially improves correct parameter usage.

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?

The description opens with a specific verb and resource: 'animate a single frame from a text description of the MOTION using the PixMiniMax engine (MiniMax H3).' It also explicitly distinguishes from a sibling tool with 'Use animate_with_text_v3 for the standard engine,' making tool selection unambiguous.

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

Usage Guidelines5/5

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

It states when to use this tool ('Best for fluid, longer clips — 4 to 40 frames'), the target use case, and names the alternative for the standard engine. The beta/subscription note and pricing details further guide appropriate usage.

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