Skip to main content
Glama

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

List MiniMax accounts

minimax_list_accounts
Read-onlyIdempotent

List the MiniMax (hailuoai.video / minimax.io) accounts added to this useapi.net API token, as stored: account id, host, maxJobs, the features it supports (video, audio, music, agent), session expiry and any stored account error. No call to MiniMax; use minimax_get_features for live credits and plan. Accounts are added on the setup page, not here. GET /accounts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely new behavior: 'No call to MiniMax' (the data is a stored snapshot, not live), that a stored account error may be present, and the underlying route GET /accounts. It stops short of describing ordering or the shape of the error field, but adds real context beyond annotations.

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?

A single tight sentence plus two short routing clauses; the resource and its returned fields come first, and each clause (no live call, setup page, endpoint) earns its place. No filler or restatement of the tool name.

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 compensates by listing exactly what the response contains, including session expiry and stored errors, and states the data is persisted rather than fetched live. An agent has everything needed to call and interpret this zero-argument tool.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing the description could clarify. It correctly implies no filtering arguments by framing the result as everything stored on the token.

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 ('List the MiniMax ... accounts added to this useapi.net API token') and immediately enumerates the fields returned (account id, host, maxJobs, features, session expiry, stored error). An agent can distinguish this list-of-accounts tool from the sibling minimax_get_features 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?

Explicitly routes the agent: 'use minimax_get_features for live credits and plan' and clarifies 'Accounts are added on the setup page, not here', which prevents a wrong attempt at account creation. No exclusion is stated for the single-account sibling minimax_get_account, 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