Skip to main content
Glama
Sign In
VideoGen MCP

VideoGen MCP

Official
by video-gen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Cancel tool execution

cancel_tool_execution
Destructive

Request cancellation of an in-progress VideoGen tool execution by providing its execution ID (vg_tool_...). Use it to stop running tasks and manage long operations.

Instructions

Request cancellation of an in-progress tool execution.

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": {
      "toolExecutionId": "<toolExecutionId>"
    },
    "name": "cancel_tool_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolExecutionIdYesTool execution id (vg_tool_...).

Output Schema

NameRequiredDescriptionDefault
errorNoError details when status is failed; otherwise null.
statusNoJob status: pending, running, succeeded, failed, or cancelled.
resultsNoGenerated results with download URLs when succeeded.
toolTypeNoTool name (e.g. GENERATE_IMAGE).
attemptIndexNoCurrent or latest attempt index.
toolExecutionIdYesTool execution id (vg_tool_...).
progressPercentageNoCompletion progress 0-100 (present after polling).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds a modest but real nuance by saying 'Request' cancellation, implying best-effort/asynchronous behavior rather than guaranteed termination, and 'in-progress' bounds which executions are eligible — but it never states what happens to partial output or whether cancellation is final.

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?

A single front-loaded sentence with no filler, which is efficient. It is borderline under-specified rather than over-concise — the brevity costs it the usage and behavioral detail it could have carried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover the destructive profile. Still, for a mutation/cleanup tool the description lacks timing semantics (immediate vs deferred cancellation), idempotency, and any note on required permissions, leaving an agent with the minimum needed to invoke it.

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 parameter and schema description coverage is 100% (the schema documents the vg_tool_... id format), so the description's single sentence adds no parameter detail. Baseline 3 applies when the schema does the heavy lifting.

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?

Specific verb (cancel) plus specific resource (tool execution), and it scopes the target to an in-progress execution, which distinguishes it from get_tool_execution/list_tool_executions. It does not, however, mention the near-identical sibling cancel_workflow_run, so an agent must infer the boundary from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given. With cancel_workflow_run sitting in the same toolset, the description offers nothing to route between cancelling a tool execution versus a workflow run, and no prerequisites (e.g. needing a live execution id) are stated.

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

Deploy Server

Other Tools