Skip to main content
Glama

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

List running agent jobs

minimax_list_agent_jobs
Read-onlyIdempotent

The agent jobs running now for this API token, grouped by account, with each jobId and its elapsed time (mm:ss), plus the accounts that can run the agent. The first check when minimax_run_agent answers 429; finished jobs are read with minimax_get_agent_job. Video and image jobs are listed by minimax_list_running_jobs. GET /agent/jobs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine context beyond that: results are grouped by account, elapsed time is formatted mm:ss, the response also includes accounts that can run the agent, and the underlying call is GET /agent/jobs. It does not mention any result cap or pagination, which is the only remaining gap.

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, then routing guidance, then the endpoint. It is dense but every clause carries information; the trailing 'GET /agent/jobs' is the only mildly expendable element, and the parentheticals make the middle sentence slightly heavy.

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, yet the description still describes the return shape — jobs grouped by account with jobId and elapsed time, plus the list of eligible accounts. Combined with the 429/rate-limit trigger and sibling routing, an agent has everything needed to call this correctly.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies no filtering inputs are accepted (scope is fixed to this API 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 the specific resource and scope: agent jobs running now for this API token, grouped by account, returning jobId and elapsed time. It also distinguishes itself from minimax_get_agent_job (finished jobs) and minimax_list_running_jobs (video/image jobs), so an agent can tell which list to call without inspecting schemas.

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?

Gives an explicit trigger — the first check when minimax_run_agent answers 429 — and names the alternatives for the two adjacent cases (finished jobs via minimax_get_agent_job, video/image jobs via minimax_list_running_jobs). Both when-to-use and when-not-to-use are covered.

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