AnimGen

Export animation

export_animation

DestructiveIdempotent

Start a paid export from an existing video asset with approved quote_id or max_credits. Changing selection or FPS creates a new export only; never regenerates source motion.

Input Schema

TableJSON Schema

Name	Required	Description
`request`	Yes
`quote_id`	No
`max_credits`	No	Approved per-operation credit cap.
`idempotency_key`	Yes	Reuse unchanged on retry; use a new key when changing the selection or FPS.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Persist this task ID immediately after create; poll it instead of creating again.
`error`	No	Task failure details, independently of any usable outputs.
`stage`	No	Current pipeline stage when available.
`object`	Yes	Public task resource type.
`status`	Yes	succeeded, failed, and cancelled are terminal; cancelling is not terminal.
`credits`	Yes	Quoted, reserved, and charged credit states.
`outputs`	No	Available assets, including partial outputs on failed/cancelled tasks. Always inspect them at a terminal state.
`metadata`	No	Caller-provided metadata.
`progress`	Yes	Fraction from 0 to 1, not a completion-time estimate.
`created_at`	Yes	UTC acceptance timestamp.
`started_at`	No	UTC production start when known.
`finished_at`	No	UTC terminal timestamp when known.
`resolved_export`	No	Persisted FPS sampling summary shared with the quote and manifest; null for legacy tasks.
`normalized_input`	No	Normalized public input; may contain private prompts or image references. Do not log wholesale.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedInput schema / $defs / ExportOptions / properties / output_formats / items / enum

Previous value: -[
-  "clip_video",
-  "webm_alpha",
-  "prores_4444",
-  "frames_zip",
-  "spritesheet",
-  "spritesheet_json",
-  "unity_meta",
-  "unity_pack",
-  "godot_pack",
-  "unreal_paper2d_pack",
-  "cocos_creator_pack",
-  "construct3_pack"
-]New value: +[
+  "clip_video",
+  "webm_alpha",
+  "prores_4444",
+  "gif",
+  "frames_zip",
+  "spritesheet",
+  "spritesheet_json",
+  "unity_meta",
+  "unity_pack",
+  "godot_pack",
+  "unreal_paper2d_pack",
+  "cocos_creator_pack",
+  "construct3_pack"
+]

Changed1 schema field changedSep 29, 2026

changedInput schema / $defs / ExportOptions / properties / output_formats / items / enum

Previous value: -[
-  "clip_video",
-  "webm_alpha",
-  "prores_4444",
-  "frames_zip",
-  "spritesheet",
-  "spritesheet_json",
-  "unity_meta",
-  "unity_pack",
-  "godot_pack",
-  "unreal_paper2d_pack",
-  "cocos_creator_pack"
-]New value: +[
+  "clip_video",
+  "webm_alpha",
+  "prores_4444",
+  "frames_zip",
+  "spritesheet",
+  "spritesheet_json",
+  "unity_meta",
+  "unity_pack",
+  "godot_pack",
+  "unreal_paper2d_pack",
+  "cocos_creator_pack",
+  "construct3_pack"
+]

AddedSep 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real context beyond annotations: the operation is paid (credits), changing selection or FPS produces a new export rather than mutating the existing one, and the source motion is never regenerated. This complements destructiveHint=true (credit spend) and idempotentHint=true without contradicting them.

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?

Two dense sentences with the cost/approval condition front-loaded and the mutation-semantics caveat second. No filler, though the second sentence packs two distinct ideas (new export only, source never regenerated) together.

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 paid mutation tool with annotations, an output schema, and a richly documented schema, the description covers the essential gaps: approval requirement, credit implication, and idempotency-on-change behavior. Only the relationship to the quote/status siblings is left to inference.

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 50%, and the description does clarify the two top-level approval parameters (quote_id / max_credits) and the selection/FPS semantics. However, it adds little on request, source_video_asset_id vs task ID, or the export option groups, so it only partially compensates for the coverage gap.

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 ('Start a paid export from an existing video asset') and identifies the two approval paths (quote_id or max_credits). It is clearly distinguishable from the read/quote/cancel siblings, though it never names an alternative explicitly.

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 a precondition for calling it (an approved quote_id or max_credits) and a rule about what happens on re-invocation with changed selection/FPS. It stops short of explicitly routing the agent to quote_animation_export first vs. using get_animation_export for status, so the workflow relationship is only implied by sibling naming.

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

All AnimGen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?