Skip to main content
Glama

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

List characters

minimax_list_characters
Read-onlyIdempotent

List the characters saved on one hailuoai.video account: characterID, characterType and the character image (file.fileID, cdnUrl). Use a file.fileID as fileID in minimax_create_video (e.g. S2V-01 subject reference) or minimax_create_template_video. Pages: page (default 1) and pageSize (default 50). Uploaded files are listed by minimax_list_files. GET /videos/characters.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
accountNoThe account id from minimax_list_accounts. Optional when you have one account, required with more.
pageSizeNoCharacters per page (default 50).

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/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds pagination defaults, single-account scoping, and the returned field set. What it does not add is ordering of results, behavior when the account has no characters, or a total count versus page contents. Solid added context beyond the annotations, but not fully 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 the core purpose and return fields, then downstream usage, then pagination, then disambiguation, then endpoint. Minor redundancy: the page/pageSize defaults repeat what the schema already says, and the endpoint tagline is nice-to-have rather than essential.

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, so the description carries the return-value burden and does it: it lists characterID, characterType and the image identifiers (file.fileID, cdnUrl). Pagination, account scoping, and cross-tool usage of the fileID are all covered, leaving nothing an agent needs in order to call this correctly.

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 description coverage is 100%, and all three parameters are already documented in the schema, so the baseline is 3. The description restates the page/pageSize defaults rather than adding meaning, and the account parameter's dependency on minimax_list_accounts is already in the schema. It adds no syntax or edge-case nuance beyond structured fields.

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?

Names a specific verb and resource ('List the characters saved on one hailuoai.video account') and enumerates the returned fields (characterID, characterType, image file.fileID, cdnUrl). It also pins the underlying endpoint GET /videos/characters, so an agent knows exactly what this retrieves versus the other list_* siblings.

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

Usage Guidelines5/5

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

Explicitly routes the agent to the right resource: characters here, uploaded files via minimax_list_files. It goes further and states the concrete downstream use of the returned file.fileID in minimax_create_video (S2V-01 subject reference) and minimax_create_template_video, which is exactly the when-to-use context an agent needs.

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