Skip to main content
Glama

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

Delete an image

minimax_delete_image
DestructiveIdempotent

Delete one image from its account's hailuoai.video history by imageId: it leaves minimax_list_images but minimax_get_image can still read it (MiniMax soft-deletes images). Answers success also for an image that does not exist or was already deleted. Cannot be undone. DELETE /images/{imageId}.

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": {
      "imageId": "<imageId>"
    },
    "name": "minimax_delete_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageIdYesThe imageId, e.g. user:12345-minimax:<account>-image:<id>.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, but the description adds value beyond them: it discloses the soft-delete semantics (still readable through minimax_get_image), that success is returned even for nonexistent or already-deleted images, and that the action cannot be undone. Those are meaningful operational details an agent cannot infer from structured fields.

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 tight, front-loaded paragraph where each sentence carries behavioral information. The trailing 'DELETE /images/{imageId}' endpoint restates the verb and resource already stated, which is minor redundancy.

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

Completeness4/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 annotations present and no output schema, the definition covers outcome semantics, idempotency behavior and the effect on sibling tools, leaving little an agent would need to guess before invoking 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?

With a single parameter and 100% schema coverage, the schema already documents imageId and its example format. The description reinforces that the delete is scoped by imageId but adds no new syntax, format or constraint detail beyond what the schema provides.

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?

Names a specific verb (delete), resource (one image), scope (from its account's hailuoai.video history) and identifier (imageId), which distinguishes it from sibling delete tools aimed at files, music, speech, video and voice.

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

Usage Guidelines4/5

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

Gives clear context for when the effect applies and points at the two relevant siblings: the image disappears from minimax_list_images but remains readable via minimax_get_image. It stops short of explicit when-to-use/when-not guidance (e.g. preferring minimax_delete_file for other resource types), so it is strong but not exhaustive.

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