gen_task_cancel_or_delete
Cancel a queued task or delete a finished one (Seedance or 3D). Destructive.
Cancelled tasks cannot be resumed; deleted tasks’ outputs are no longer retrievable. The call is refused unless expected_status matches the task’s actual status.
| Requirement | Value |
|---|---|
| Registration | Requires BYTEPLUS_MODELARK_API_KEY. |
| Execution | Foreground only |
| Required permission | gen:delete |
This site lists the full configured capability surface, not the tools enabled on your particular server. Use model discovery and job discovery to check your connection. Credentials are server configuration, never tool arguments.
Ask your connected AI client to use gen_task_cancel_or_delete for the operation you want.
The client constructs the arguments and handles tool calls. Review its proposed
operation before approving anything billable. For a non-billable introduction,
start with discovery without generation.
Call this tool directly. It is not a background-job target.
Match the input fields below and the full JSON Schema. See the worked examples for this capability and Background Execution for job/result handling.
An Ark job ID is not a provider task ID. Video and 3D tasks use gen_task_get, VOD tasks use vod_get_task, and avatars use omnihuman_get_task. Save accepted provider task IDs and resume polling instead of submitting a second generation.
Inputs
Section titled “Inputs”The MCP arguments object wraps these fields as {"input": {...}}.
| Field | Type | Required | Description and constraints |
|---|---|---|---|
confirm |
true | No | Must be true to confirm this destructive action.; Default: true |
expected_status |
“queued”, “succeeded”, “failed”, “expired” | Yes | Status you expect the task to be in; the call is refused if it differs. |
mode |
“cancel”, “delete” | Yes | ‘cancel’ stops a queued task; ‘delete’ removes a terminal task’s record. |
task_id |
string | Yes | Generation task ID (Seedance, Hyper3D or Hitem3d). |
Outputs
Section titled “Outputs”| Field | Type | Required | Description and constraints |
|---|---|---|---|
message |
string | Yes | Human-readable confirmation message. |
mode |
“cancel”, “delete” | Yes | The action performed: cancel or delete. |
previous_status |
string | Yes | The task’s status before the action was applied. |
task_id |
string | Yes | The task ID that was cancelled or deleted. |
Nested Types
Section titled “Nested Types”Field types named above refer to these shared definitions. Optional/null fields, enum choices and bounds are retained in the complete schemas below. Schema validation is followed by runtime capability and security checks.
GenTaskCancelOrDeleteInput
| Field | Type | Required | Description and constraints |
|---|---|---|---|
confirm |
true | No | Must be true to confirm this destructive action.; Default: true |
expected_status |
“queued”, “succeeded”, “failed”, “expired” | Yes | Status you expect the task to be in; the call is refused if it differs. |
mode |
“cancel”, “delete” | Yes | ‘cancel’ stops a queued task; ‘delete’ removes a terminal task’s record. |
task_id |
string | Yes | Generation task ID (Seedance, Hyper3D or Hitem3d). |
Complete JSON Schemas
Section titled “Complete JSON Schemas”Input schema, including the MCP wrapper
{ "$defs": { "GenTaskCancelOrDeleteInput": { "description": "Input model for ``gen_task_cancel_or_delete``.", "properties": { "confirm": { "const": true, "default": true, "description": "Must be true to confirm this destructive action.", "type": "boolean" }, "expected_status": { "description": "Status you expect the task to be in; the call is refused if it differs.", "enum": [ "queued", "succeeded", "failed", "expired" ], "type": "string" }, "mode": { "description": "'cancel' stops a queued task; 'delete' removes a terminal task's record.", "enum": [ "cancel", "delete" ], "type": "string" }, "task_id": { "description": "Generation task ID (Seedance, Hyper3D or Hitem3d).", "type": "string" } }, "required": [ "task_id", "mode", "expected_status" ], "type": "object" } }, "additionalProperties": false, "properties": { "input": { "$ref": "#/$defs/GenTaskCancelOrDeleteInput" } }, "required": [ "input" ], "type": "object"}Output schema, including nested definitions
{ "description": "Output model for ``gen_task_cancel_or_delete``.", "properties": { "message": { "description": "Human-readable confirmation message.", "title": "Message", "type": "string" }, "mode": { "description": "The action performed: cancel or delete.", "enum": [ "cancel", "delete" ], "title": "Mode", "type": "string" }, "previous_status": { "description": "The task's status before the action was applied.", "title": "Previous Status", "type": "string" }, "task_id": { "description": "The task ID that was cancelled or deleted.", "title": "Task Id", "type": "string" } }, "required": [ "task_id", "mode", "previous_status", "message" ], "title": "GenTaskCancelOrDeleteOutput", "type": "object"}Troubleshooting
Section titled “Troubleshooting”- Missing tool: check provider credentials and feature flags, then restart the connection.
- Invalid arguments: keep the correct wrapper and follow current model limits from discovery. A valid schema alone does not prove the chosen model supports the combination.
- A job completes with an error: inspect the original tool result, not only the outer job status. Never automatically resubmit potentially billable work.
- Local output writes from jobs require server-configured
OUTPUT_ROOTS; HTTP cannot write to a client’s local disk.
See configuration, background execution, and artifact delivery.