Skip to main content
Glama

MiniMax MCP Server by useapi.net (third-party)

Cancel a running video

minimax_cancel_video
DestructiveIdempotent

Ask MiniMax to cancel a video that is still generating, by videoId (from minimax_create_video or minimax_list_running_jobs). An empty success means MiniMax accepted the request; read minimax_get_video for the video's final status. To only stop this API tracking a job use minimax_stop_tracking; to remove a finished video use minimax_delete_video. Cannot be undone. POST /videos/cancel.

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": {
      "videoId": "<videoId>"
    },
    "name": "minimax_cancel_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesThe videoId of a running video.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds semantics annotations cannot express: the response is only an acceptance acknowledgement ('An empty success means MiniMax accepted the request') and the final outcome must be polled via minimax_get_video. 'Cannot be undone' largely restates destructiveHint, and there is no mention of auth or rate limits, keeping it just short of the top score.

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?

Three dense sentences, front-loaded with the action and identifier, followed by response semantics and then the disambiguation clauses. Every sentence carries distinct information and the endpoint is appended compactly.

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?

For a single-parameter, no-output-schema mutation, it discloses the irreversible nature, the meaning of an empty response, and the follow-up call needed to confirm the result. Nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is already documented, so baseline would be 3. The description adds real value by specifying provenance for videoId and constraining it to *running* videos, which tells the agent the call fails or is pointless on completed jobs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('cancel a video that is still generating') plus the keying parameter ('by videoId'). It also names the two sibling tools it must not be confused with (minimax_stop_tracking, minimax_delete_video), so an agent can discriminate without opening another schema.

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

Usage Guidelines5/5

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

Explicitly covers when to use this tool ('a video that is still generating'), where the identifier comes from (minimax_create_video or minimax_list_running_jobs), and two named alternatives with the exact conditions that select them (stop tracking vs. delete a finished video). No inference required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources