AnimGen

Cancel video generation

cancel_video_generation

DestructiveIdempotent

Request cancellation of an owned source-video task. Inspect cancellation_allowed and cancellation_reason. Seedance and V1 HappyHorse reject cancellation after submission starts (GENERATION_ALREADY_SUBMITTED). V1 MiniMax queued cancellation requires remote confirmation. Keep polling the original task even if cancellation is uncertain; cancellation does not guarantee a refund.

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

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: inspect cancellation_allowed and cancellation_reason, model-specific rejection codes, remote confirmation for certain queued tasks, continued polling after uncertain cancellation, and no refund guarantee. These details materially inform how an agent should interpret and handle cancellation outcomes.

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 front-loaded with the core action, followed by inspection guidance, model-specific constraints, and post-cancellation behavior. Every sentence carries operational value with no filler.

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?

Given the presence of annotations and an output schema, the description supplies the key behavioral context needed to invoke and reason about cancellation. It covers eligibility checks, model-specific exceptions, polling behavior, and refund caveats.

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?

There is one required parameter, task_id, but schema description coverage is 0%. The description implies an owned source-video task but does not explain task_id semantics, where to obtain it, or how it relates to sibling tools. The type and UUID format in the schema do most of the work.

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 and resource: 'Request cancellation of an owned source-video task.' This clearly distinguishes the operation from generation or retrieval, though it does not explicitly contrast with sibling tools such as cancel_animation or get_video_generation.

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 context and several when-not conditions, including model-specific rejection after submission starts and remote confirmation requirements for V1 MiniMax queued cancellations. It does not name an alternative sibling tool for checking task status, but the operational conditions are explicit.

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?