Skip to main content
Glama

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

List images

minimax_list_images
Read-onlyIdempotent

List one account's images on hailuoai.video, including running ones and those made in the web app: imageId, statusLabel, URLs, fileID and prompt (desc). Pages of limit items (default 30); pass the last imageId as lastImageId for the next page while hasNext is true. Deleted images are not listed. GET /images.

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

Input Schema

NameRequiredDescriptionDefault
limitNoImages per page (default 30).
accountNoThe account id from minimax_list_accounts. Optional when you have one account, required with more.
lastImageIdNoThe last imageId of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds useful context beyond that: running images appear, deleted images are excluded, and pagination terminates on hasNext. No rate limits, auth or ordering details are given, so it is solid but not rich.

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 purpose, then return fields, then pagination mechanics, then an exclusion note — a sensible order with no filler. It is dense to the point of reading as one long run-on, which slightly hurts scanability.

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?

With no output schema, the description carries the return-value burden and does list the returned fields (imageId, statusLabel, URLs, fileID, prompt). Pagination and the deleted-image exclusion are covered; only ordering and total-count behavior are left unstated, which is a minor gap.

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 coverage is 100%, so all three parameters are already documented, and the description largely restates limit's default page size and lastImageId's meaning. The one genuine addition is the pagination loop condition (advance while hasNext is true) and the account-optional-vs-required rule, which is a modest supplement over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb+resource: lists one account's images on hailuoai.video, and it scopes the set explicitly (including running images and web-app-created ones, excluding deleted). The resource name 'images' separates it from list_videos/list_files/list_music siblings, though it never names an alternative outright.

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

Usage Guidelines3/5

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

Gives concrete operational guidance: paginate by passing the last imageId while hasNext is true, and account is optional with one account but required with more. It stops short of saying when to use this versus minimax_get_image for a single item or minimax_list_files, so the routing is only implied.

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