Skip to main content
Glama

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

List running jobs

minimax_list_running_jobs
Read-onlyIdempotent

The videos, images, music and speech this API is tracking now (videoId / imageId / musicId / audioId, started, elapsed mm:ss) and the accounts with a free video slot (account, maxJobs, executing, available). The first check when a create tool answers 429 (accounts at maxJobs); everything on an account, web app included, is in minimax_list_videos / minimax_list_images. GET /scheduler and GET /scheduler/available.

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

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 cover read-only, idempotent, non-destructive behavior, and the description adds substantive context: the payload shape (videoId/imageId/musicId/audioId, started, elapsed mm:ss; account, maxJobs, executing, available) and the underlying endpoints GET /scheduler and GET /scheduler/available. It stops short of saying whether results are paginated or how often the snapshot refreshes, so it is not fully exhaustive.

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?

Three tight sentences with the primary purpose front-loaded and the 429 use case placed where an agent will see it. The heavy parenthetical field dumps make it dense and slightly hard to scan, but no sentence is filler.

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 burden of describing what comes back, and it does so at field level for both result sets. Combined with the 429 guidance and endpoint references, an agent has what it needs; only refresh/pagination behavior and the meaning of 'available' slots are 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?

The tool takes no parameters, so there is no parameter semantics to add and the baseline is 4. The parenthetical field lists describe return content rather than inputs, which is still useful but does not change the parameter picture.

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?

The description names the exact resource ('the videos, images, music and speech this API is tracking now') plus the secondary resource (accounts with a free video slot), and enumerates the returned fields. It also explicitly distinguishes itself from minimax_list_videos / minimax_list_images, which hold the full per-account listing.

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?

It gives an explicit triggering condition: 'the first check when a create tool answers 429 (accounts at maxJobs)'. It also implies the exclusion — for a complete account-wide inventory use minimax_list_videos / minimax_list_images — so the agent can route between this and its siblings without inference.

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