AnimGen

Get video generation

get_video_generation

Read-onlyIdempotent

Poll an owned source-video task, including partial outputs, measured media metadata and credit state.

Input Schema

Name	Required	Description	Default
`task_id`	Yes

Output 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.
`cancellation_reason`	No	Stable reason when cancellation is unavailable: TASK_TERMINAL, CANCELLATION_PENDING, CANCELLATION_NOT_CONFIRMED, or GENERATION_ALREADY_SUBMITTED.
`cancellation_allowed`	No	Whether a cancellation request can currently be accepted. Remote cancellation still needs confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

addedOutput schema / properties / cancellation_allowed

Added value: +{
+  "default": false,
+  "description": "Whether a cancellation request can currently be accepted. Remote cancellation still needs confirmation.",
+  "title": "Cancellation Allowed",
+  "type": "boolean",
+  "x-description-zh": "当前是否允许受理取消请求；远端取消仍须确认。"
+}

addedOutput schema / properties / cancellation_reason

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stable reason when cancellation is unavailable: TASK_TERMINAL, CANCELLATION_PENDING, CANCELLATION_NOT_CONFIRMED, or GENERATION_ALREADY_SUBMITTED.",
+  "title": "Cancellation Reason",
+  "x-description-zh": "不可取消的稳定原因：TASK_TERMINAL、CANCELLATION_PENDING、CANCELLATION_NOT_CONFIRMED 或 GENERATION_ALREADY_SUBMITTED。"
+}

AddedSep 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that by noting partial outputs, measured media metadata, credit state, and the ownership constraint.

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 a single well-formed sentence with the operation front-loaded and no wasted words. It efficiently packs the scope and key return details.

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?

The output schema is available, so the description need not fully document return values, and annotations cover the safety profile. It is nearly complete for a simple polling tool, with the main gap being the unexplained task_id parameter.

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

Parameters2/5

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

Schema description coverage for the single task_id parameter is 0%, so the description should compensate but does not. It refers only to a 'source-video task' and never explains that task_id is the identifier returned by a generation or quote operation.

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?

The description states a specific verb ('Poll') and a specific resource ('owned source-video task'), making the core action clear. It distinguishes itself reasonably from generation/cancellation siblings, though it does not explicitly name an alternative such as preview_video or generate_video.

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?

Usage is implicitly clear: this is a polling tool for an owned source-video task. However, it does not explicitly state when to use it instead of alternatives like preview_video, nor does it mention that the task_id typically comes from generate_video.

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?