Skip to main content
Glama

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

Get an image

minimax_get_image
Read-onlyIdempotent

One image by imageId (from minimax_create_image or minimax_list_images): status label (pending, queued, processing, completed, failed, moderated) and, once completed, its url (videoURL), downloadURL (no watermark, paid accounts), size and fileID (reusable as a reference), with the image itself as an image block. wait: true waits up to ~50 s. Deleted images can still be read here. GET /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_get_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish (default false: one read).
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.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so the baseline is low, yet the description still adds real behavior: the six possible status labels, that url/downloadURL/size/fileID only appear once completed, that downloadURL is watermark-free only on paid accounts, that an image block is returned, and that deleted images remain readable. It does not mention eventual consistency or errors on invalid ids, so it falls short of a 5.

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?

Front-loaded with the resource and scope, and every clause (status labels, downloadURL caveat, fileID reuse, wait timing, deleted-image note) carries usable information. It is a single dense sentence-heavy block with stacked parentheticals, which slightly hurts scannability.

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?

With no output schema, the description fully carries the return-value burden: it names the status field, the completion-gated fields, the fileID reuse, and the embedded image block. Nothing an agent needs to call this correctly, including the wait semantics and deleted-image edge case, is missing.

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 adds meaning the schema lacks: imageId provenance from minimax_create_image/minimax_list_images, and the practical consequence of wait (up to ~50 s instead of a single read). The id format example itself is already in the schema, so the gain is incremental rather than transformative.

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 and resource (fetch one image by imageId) and immediately names the sibling tools that produce that id (minimax_create_image, minimax_list_images), so it is distinguishable from minimax_list_images. The enumerated status labels and returned fields make the purpose unambiguous.

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?

The description tells the agent where the imageId comes from (create or list) and explains the wait switch as one-read versus a ~50 s poll, which implicitly covers the polling use case. It never states when not to use it versus minimax_list_images, so guidance 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