Skip to main content
Glama

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

Upload a reference file

minimax_upload_file

Upload your own image (PNG, JPEG, WebP), audio (MP3, WAV) or MP4 video to one account, for use as a reference in minimax_create_video (fileID, end_frame_fileID, omni slots), minimax_create_image (characterFileId, referenceFileIdN) or minimax_create_template_video. Send a public https url or contentBase64 (small files), up to 50 MB here; larger files (the REST takes up to 5 GB) go to POST /files directly. Returns a fileID that works on that account only, and its ossPath. POST /files.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "minimax_upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public https URL of the file.
accountNoThe account id from minimax_list_accounts. Optional when you have one account, required with more.
mimeTypeNoThe file's type. Default: from the url's answer. image/webp is sent as image/jpeg, as POST /files expects.
contentBase64NoThe file content, base64-encoded (instead of url).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only mark this as a non-read-only, non-idempotent, non-destructive open-world write; the description adds real substance beyond that: a 50 MB ceiling with the REST fallback, the fact that the returned fileID is scoped to a single account, and the returned ossPath. It stops short of stating retention lifetime or whether re-uploading the same file creates duplicates.

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?

Dense but front-loaded: the accepted formats and the purpose come first, then the downstream consumers, then the size caveat. The parenthetical list of every downstream slot name is slightly noisy, but it is the routing information an agent actually needs.

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?

There is no output schema, and the description compensates by naming the two returned values (fileID, ossPath) and their account scoping. Combined with a fully documented 4-parameter schema, an agent has everything needed to pick a source (url or base64), pick an account, and use the result.

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%, so the baseline is 3, but the description earns more by clarifying the url-vs-contentBase64 tradeoff (base64 only for small files) and by tying fileID to the downstream tools. The mimeType webp-to-jpeg coercion and the account requirement are already stated in the schema, so no extra credit there.

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 (upload) plus the accepted resource types (PNG/JPEG/WebP, MP3/WAV, MP4) and explicitly names the three consumer tools and the exact parameter slots (fileID, end_frame_fileID, characterFileId, referenceFileIdN) the resulting id feeds. An agent can distinguish this from the create_* siblings without opening any 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?

Gives clear when-to-use context (to obtain a reference asset for create_video/create_image/create_template_video) and an explicit alternative path: files over 50 MB must go to POST /files directly, which the REST accepts up to 5 GB. It does not, however, distinguish itself from the sibling upload tools minimax_upload_music_reference or minimax_upload_voice_sample, so an agent handling audio must infer the split itself.

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