Skip to main content
Glama

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

Get a video

minimax_get_video
Read-onlyIdempotent

One video by videoId (from minimax_create_video, minimax_create_template_video or minimax_list_videos): status label (pending, queued, processing, completed, failed, moderated), percent and message while it runs, and once completed width, height, videoURL, downloadURL (no watermark, paid accounts) and coverURL. wait: true waits up to ~50 s. A 404 usually means the video was moderated and removed. GET /videos/{videoId}.

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": {
      "videoId": "<videoId>"
    },
    "name": "minimax_get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish (default false: one read).
videoIdYesThe videoId, e.g. user:12345-minimax:<account>-video:<id>.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them: it enumerates the status lifecycle (pending, queued, processing, completed, failed, moderated), describes partial progress fields while running, lists the fields returned on completion, and explains the ~50 s wait ceiling and 404 semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense, front-loaded sentence that leads with what is returned, then the wait behavior, then the 404 edge case, then the underlying endpoint. Every clause carries distinct information; there is no filler.

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 must carry the return shape — and it does, listing both in-progress and completed fields plus the failure/moderated path. For a two-parameter polling read tool, nothing an agent needs in order to call it correctly is missing.

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 real meaning: it gives the provenance of videoId (the three producing tools) and explains the tradeoff of wait (blocking ~50 s vs. one read), not just its type and default. The ID format example still lives only in the schema, so it stops short of 5.

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 verb and resource ("One video by videoId") and immediately disambiguates it from siblings by naming minimax_list_videos and the two create tools as the source of the ID. An agent can pick this over minimax_list_videos without opening either 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 guidance: where videoId comes from (create or list tools), when to set wait (true to block ~50 s, default false for a single read), and how to interpret a 404 (likely moderated/removed). Clear context, though it does not explicitly state exclusions such as when polling this is inferior to minimax_list_running_jobs.

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