Skip to main content
Glama

minimax_get_task

Check a video generation task's status and retrieve completed video URLs and metadata. Use it to confirm completion or get full details of generated videos.

Instructions

Query the status and result of a video generation task.

Use this to check if a generation is complete and retrieve the resulting
video URLs and other metadata.

Use this when:
- You want to check if a generation has completed
- You need to retrieve video URLs from a previous generation
- You want to get the full details of a generated video

Task states:
- 'queued' or 'running': Generation is still in progress
- 'succeeded': Generation finished successfully
- 'failed' or 'cancelled': Generation reached a terminal error state

Returns:
    Task status and generated video information including URLs and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task ID returned from a generation request. This is the 'task_id' field from any minimax_generate_* tool response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations, so the description bears the transparency load. It explains the read-only nature implicitly and describes possible states, but does not explicitly state it is side-effect-free. Still, the behavior is well described.

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?

Concise and well-organized with bullet-like lists for use cases and states. No redundant information, every sentence adds value.

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?

For a simple query tool, the description covers purpose, usage, states, and return content. It is sufficient for an agent to understand when and how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter task_id is fully explained both in the schema and in the description, including its origin from generation requests. Coverage is 100%.

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 clearly states the tool's purpose: 'Query the status and result of a video generation task.' It is specific and distinguishes from sibling tools like generate, list, and delete.

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?

Provides explicit use cases ('check if a generation is complete', 'retrieve the resulting video URLs'), and lists task states to inform polling behavior. No ambiguity about when to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/MinimaxMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server