Skip to main content
Glama

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

Delete a video

minimax_delete_video
DestructiveIdempotent

Delete one video from its account's hailuoai.video history by videoId. Answers success also for a video that does not exist or was already deleted. To stop a video that is still generating use minimax_cancel_video. Cannot be undone. DELETE /videos/{videoId}.

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_delete_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesThe videoId, e.g. user:12345-minimax:<account>-video:<id>.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description does not need to re-establish safety. It nevertheless adds genuinely non-obvious behavior: success is returned even for a nonexistent or already-deleted video, and the deletion is permanent. It stops short of covering auth/permission requirements or what the success payload looks like beyond 'success'.

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 short sentences, front-loaded with the action and identifier, then the idempotent-success caveat, then the alternative tool, then the irreversibility warning and endpoint. No filler; each sentence carries a distinct operational fact.

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?

The tool has one required parameter at full schema coverage, no output schema, and annotations that already cover the safety profile. The description closes the two remaining gaps an agent would hit in practice — ambiguous outcome on a missing video and irreversibility — so nothing material is missing.

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 description coverage is 100% and the videoId property already documents its compound format with an example. The description only restates that the id scopes the delete to one video in that account's history, adding little beyond the schema. Baseline 3 applies.

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?

Specific verb (delete) plus resource (one video) plus scope (from its account's hailuoai.video history) plus identifier (by videoId). It also names the sibling minimax_cancel_video that an agent might otherwise confuse it with, so the tool is distinguishable from the surrounding delete_*/cancel_* family.

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 routes the agent: 'To stop a video that is still generating use minimax_cancel_video.' That is a stated when-not-to-use condition paired with a named alternative, which is exactly the guidance needed given several overlapping delete tools.

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