Skip to main content
Glama

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

Get an agent job

minimax_get_agent_job
Read-onlyIdempotent

One agent job by jobId (from minimax_run_agent or minimax_list_agent_jobs): status (started, completed, failed), the agent's message and, once completed, each file it made with fileName, type, fileUrl and no_watermark_url (videos); a failure's reason. wait: true waits up to ~50 s. Jobs are kept 31 days. GET /agent/{jobId}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jobId": "<jobId>"
    },
    "name": "minimax_get_agent_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish (default false: one read).
jobIdYesThe jobId, e.g. p<project>-u12345-a<account>-bot:minimax.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/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), and the description adds real behavior: the job lifecycle states, a 31-day retention window, the ~50 s wait cap, and that failure reasons are returned. It leaves the timeout case unspecified (what is returned if wait expires before completion).

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?

Compact and front-loaded: identity and source of jobId first, then returned fields, then the wait and retention caveats. Some of the wait wording duplicates the schema, but nothing is wasted.

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 properly enumerates what comes back (status, message, output files with fileName/type/fileUrl/no_watermark_url, failure reason) and adds retention. Only the behavior when wait times out before completion is left implicit.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: jobId's provenance and format context, and that wait=true blocks up to roughly 50 seconds versus a single read by default. That goes beyond the schema's phrasing.

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 resource and scope: 'One agent job by jobId', and names the two sibling tools that produce a jobId (minimax_run_agent, minimax_list_agent_jobs). This clearly separates it from minimax_list_agent_jobs, which returns many jobs.

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?

It tells the agent where the jobId comes from and when to set wait=true (blocking up to ~50 s), which implies the polling use case. It does not explicitly say when to prefer listing jobs or when to poll repeatedly instead of waiting, so it falls short of full when/when-not guidance.

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