Skip to main content
Glama

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

Stop tracking a job

minimax_stop_tracking
DestructiveIdempotent

Stop this API tracking a running video, image, music or speech job (an id from minimax_list_running_jobs) and free its slot on the account. It does not cancel the work at MiniMax: a video or song carries on and its get tool still finds it, but a stopped speech audioId reads as failed from then on. To ask MiniMax to stop a video use minimax_cancel_video. 404 when the id is not running. Cannot be undone. DELETE /scheduler/{id}.

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": {
      "id": "<id>"
    },
    "name": "minimax_stop_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA videoId, imageId, musicId or audioId that is running.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructive/idempotent/openWorld but say nothing about consequences; the description supplies them: the work is NOT cancelled at MiniMax, video and song keep running and remain fetchable, a stopped speech audioId reads as failed thereafter, and the action "Cannot be undone." It also names the underlying call (DELETE /scheduler/{id}). No contradiction with idempotentHint — idempotency concerns repeated calls, not reversibility.

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?

Four compact sentences, front-loaded with the action and effect, then the crucial caveat, the alternative, and the error/verb detail. No filler and nothing repeated from the title.

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 one-parameter destructive tool with no output schema, everything needed is present: id source, side effects by asset type, irreversibility, error condition, and the sibling to use for real cancellation.

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?

Schema coverage is 100% and the single parameter already documents the id as a running videoId/imageId/musicId/audioId, so the schema does the heavy lifting. The description adds the id's provenance (from minimax_list_running_jobs) and the per-type consequence of stopping, but nothing about format or validation beyond the schema.

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+resource ("Stop this API tracking a running video, image, music or speech job") plus the effect ("free its slot on the account") and cites the source of the id (minimax_list_running_jobs). It explicitly distinguishes itself from minimax_cancel_video, so an agent can separate the two without reading schemas.

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?

Gives when-to-use (stop tracking a running job by id from minimax_list_running_jobs), when-not-to-use ("To ask MiniMax to stop a video use minimax_cancel_video"), and the failure condition ("404 when the id is not running"). Alternatives and exclusions are both covered.

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