Skip to main content
Glama

Animate scenes

animate_scenes
Destructive

Film the scenes you name, or every scene whose still is ready and whose clip is not. This spends credits and returns as soon as the work is dispatched; poll get_storyboard. A scene is animated from its own still, so generate the stills first and look at them — a clip of a ruined frame costs the same as a clip of a good one. A morph travels from this scene's still to another scene's, and NEVER describe the transformation in the motion prompt: the model is already interpolating between the two frames, and a prompt that also describes the change makes it happen twice. A morph has one destination and a model belongs to one take, so both are refused on more than one scene rather than half-applied after the credits are gone. Pass quote to price the batch without filming anything.

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": {
      "storyboard_id": "<storyboard_id>"
    },
    "name": "animate_scenes"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
quoteNo
scenesNo
all_readyNo
referencesNo
storyboard_idYes
idempotency_keyNo
morph_into_sceneNo
reference_scenesNo
reference_videosNoA clip whose camera and timing the model should follow — what match_scene_motion answers with. One scene only.

Output Schema

NameRequiredDescriptionDefault
castYes
briefYes
notesYes
quoteNo
textsYes
scenesYes
soundsYes
videosYes
creditsYes
historyYes
messageYes
skippedNo
startedNo
stoppedNo
acceptedNo
receiptsNo
scheduleYes
settingsYes
referenceNo
storyboardYes
download_urlNo
generation_idNo
remaining_scenesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / model / enum
      Previous value: -[
      -  "seedance-2.5",
      -  "seedance-2.5-spicy",
      -  "seedance-2.0",
      -  "seedance-2.0-mini",
      -  "seedance-2.0-fast",
      -  "grok-imagine-video-1.5",
      -  "veo-3.1",
      -  "veo-3.1-fast",
      -  "veo-3.1-lite",
      -  "gemini-omni-1.1",
      -  "kling-v3-omni-video",
      -  "kling-v3-video",
      -  "happyhorse-1.0",
      -  "wan-3",
      -  "wan-3-prime",
      -  "gen-4.5",
      -  "p-video",
      -  "p-video-2",
      -  "flux-3",
      -  "minimax-h3-max",
      -  "p-video-avatar",
      -  "p-video-animate",
      -  "p-video-replace",
      -  "omni-human-1.5",
      -  "kling-avatar-v2",
      -  "kling-v3-motion-control",
      -  "kling-lip-sync",
      -  "sync-lipsync-2",
      -  "genjutsu-motion-transfer",
      -  "genjutsu-object-swap"
      -]New value: +[
      +  "seedance-2.5",
      +  "seedance-2.0",
      +  "seedance-2.0-mini",
      +  "seedance-2.0-fast",
      +  "grok-imagine-video-1.5",
      +  "veo-3.1",
      +  "veo-3.1-fast",
      +  "veo-3.1-lite",
      +  "gemini-omni-1.1",
      +  "kling-v3-omni-video",
      +  "kling-v3-video",
      +  "happyhorse-1.0",
      +  "wan-3",
      +  "wan-3-prime",
      +  "gen-4.5",
      +  "p-video",
      +  "p-video-2",
      +  "flux-3",
      +  "minimax-h3-max",
      +  "p-video-avatar",
      +  "p-video-animate",
      +  "p-video-replace",
      +  "omni-human-1.5",
      +  "kling-avatar-v2",
      +  "kling-v3-motion-control",
      +  "kling-lip-sync",
      +  "sync-lipsync-2",
      +  "genjutsu-motion-transfer",
      +  "genjutsu-object-swap"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructive/non-idempotent annotations, it states that credits are spent, the call returns after dispatch rather than completion, polling is required, and morph/model multi-scene misuse is refused before half-applying. It also warns that a bad still costs the same as a good one, which is exactly the kind of behavioral context an agent needs.

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?

Despite its length, the description is front-loaded and every sentence carries useful information: async dispatch, credit spend, still quality, morph prompt caveat, all-or-nothing constraints, and quote dry run. There is no filler or repeated schema content.

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 destructive, asynchronous, credit-spending batch tool, the description covers the essential operational context: when to use it, what happens after invocation, what to poll, quality prerequisites, morph constraints, and how to preview cost. An output schema exists, so return-value detail is not required.

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?

With only 10% schema description coverage across 10 parameters, the description does explain key semantics for scenes/all_ready, quote, morph_into_scene, and the one-take model constraint, and reference_videos has schema text. However, it leaves references, reference_scenes, idempotency_key, and several other parameters without descriptive meaning, so it only partially compensates for the low schema coverage.

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: it films named scenes or every scene whose still is ready but clip is missing. That clearly distinguishes this storyboard-level batch animation operation from generic image/clip generation, and it names the morph behavior this tool supports.

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 clear usage conditions: generate stills first, inspect them, use quote to price without filming, and poll get_storyboard after dispatch. It does not explicitly route one-off cases to siblings like animate_image or generate_clip, but the storyboard-scene context and prerequisites are well defined.

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.

Resources