Skip to main content
Glama

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

Delete an uploaded file

minimax_delete_file
DestructiveIdempotent

Delete one uploaded reference file from its account by fileID (from minimax_upload_file or minimax_list_files); generations that already used it are not affected. Answers success also for a file that does not exist or was already deleted. Cannot be undone. DELETE /files/{fileID}.

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": {
      "fileID": "<fileID>"
    },
    "name": "minimax_delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIDYesThe fileID, e.g. user:12345-minimax:<account>-file:<id>.

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?

Goes well beyond the annotations: it discloses that deletion is irreversible, that downstream generations are unaffected, and that success is returned even when the file does not exist or was already deleted — explaining the meaning of idempotentHint in practice. This is exactly the kind of side-effect scope an agent needs before invoking a destructive tool.

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 clauses, each carrying distinct information: target, provenance, side-effect scope, idempotent success semantics, irreversibility, and the endpoint. Nothing is redundant or repeated from the annotations.

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 destructive tool with no output schema, the description covers everything needed: how to obtain the ID, what is and isn't affected, that the operation is irreversible, and what a success response implies. No material gap remains.

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 schema already gives the fileID format example, so the baseline is 3; the description adds provenance by naming the tools that supply the value. No additional syntax or validation detail is offered beyond that.

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 ('Delete') and a precisely scoped resource ('one uploaded reference file ... by fileID'), which distinguishes it from sibling deletes such as minimax_delete_image or minimax_delete_voice. It also names the sibling tools that produce the fileID, so an agent can place it in the upload/list/delete workflow without opening a schema.

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?

Tells the agent where the fileID comes from (minimax_upload_file or minimax_list_files) and clarifies that generations already using the file are unaffected, which is the main ambiguity an agent would have before deleting. It stops short of stating exclusions (e.g. that it does not apply to images/music/video assets), which the sibling list makes relevant.

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