Skip to main content
Glama

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

List uploaded files

minimax_list_files
Read-onlyIdempotent

List the reference files uploaded to one account (with minimax_upload_file, POST /files or the MiniMax web app): file_id (the fileID for the create tools), file_name, file_type, cdn_url and oss_path (the ossPath minimax_create_template_video needs). limit sets how many (default 50). Characters made in the web app are listed by minimax_list_characters. GET /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_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many files to return (default 50).
accountNoThe account id from minimax_list_accounts. Optional when you have one account, required with more.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the description's job is added context, and it delivers: the underlying endpoint (GET /files), the default page size, the account scoping behavior, and the exact field set returned. No pagination/offset behavior is mentioned, which is the only notable gap for a list endpoint.

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 purpose before the parenthetical detail, and every clause carries information (source tools, returned fields, default, sibling exclusion). It is dense to the point of being a single breathless sentence with stacked parentheses, which costs a little readability.

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 so by enumerating file_id, file_name, file_type, cdn_url, oss_path with their downstream meanings. Combined with the account-scoping and default-limit notes, an agent has what it needs to call it correctly; only response shape (e.g., ordering, truncation) is unspecified.

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% and both parameters are documented in the schema, so baseline is 3. The description reinforces that account ids come from minimax_list_accounts and clarifies limit's default, but adds no new syntax or constraint beyond the schema.

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?

Opens with a specific verb and resource ('List the reference files uploaded to one account') and immediately distinguishes the resource from the sibling set by noting 'Characters made in the web app are listed by minimax_list_characters.' An agent can tell it apart from minimax_list_images/videos/voices 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?

Gives concrete downstream use: file_id is 'the fileID for the create tools' and oss_path is 'the ossPath minimax_create_template_video needs,' plus it names minimax_upload_file and the web app as the ways files arrive. It also states the account-selection rule ('optional when you have one account, required with more'). It stops short of an explicit when-not statement beyond the characters exclusion.

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