Skip to main content
Glama

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

Generate a template video

minimax_create_template_video

Generate a video from a hailuoai.video agent template (templateId from minimax_list_agent_templates), with the prompt and / or image the template requires (check it with minimax_list_agent_templates and templateId). Uses the account's MiniMax credits (the template's credits). Waits up to ~50 s, then returns the videoId for minimax_get_video; free-form generation is minimax_create_video. POST /videos/agent-create.

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": {
      "templateId": "<templateId>"
    },
    "name": "minimax_create_template_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish (default true); false returns the id at once.
fileIDNoThe image for a template that requires one (with ossPath): a fileID from minimax_upload_file, minimax_list_files, minimax_list_characters or a completed image (minimax_get_image), on the same account.
promptNoText for a template that requires it; refused by one that does not. Up to 2,000 characters.
accountNoThe account to use; with a fileID it must be the file's account: the account id from minimax_list_accounts. Omit to let the API pick one of your accounts.
maxJobsNoOverride the account's maxJobs (generations at once) for this request, 1-10.
ossPathNoThe ossPath of that fileID (minimax_upload_file's ossPath, minimax_list_files' oss_path). Required with fileID, only with it.
replyRefNoOptional reference of yours, stored and returned with the result and webhook. Up to 1,024 characters.
replyUrlNoOptional webhook: the API POSTs the finished result (same shape as the get tool's record) to this URL. Up to 1,024 characters.
templateIdYesThe template id.

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 declare non-readOnly, open-world, non-idempotent and non-destructive; the description adds value on top by disclosing credit consumption, the ~50 s wait behavior, the returned videoId and the handoff to minimax_get_video. It does not cover failure modes or what happens when credits are exhausted or the wait times out, so it stops short of fully rich behavioral context.

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?

One dense but front-loaded passage: purpose and template source first, then cost/return, then the sibling alternative and endpoint. Every clause carries information an agent needs, with no filler; the only roughness is the 'prompt and / or image' phrasing.

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?

For a 9-parameter generation tool with no output schema, the description covers the discovery step, the requirements coupling, cost, latency, the returned videoId and the follow-up get tool. What is missing is edge-case behavior when the template's requirements are not met or when wait=false is used with a long job, but the core call path is complete.

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 the schema does not: templateId must come from minimax_list_agent_templates, and whether prompt and/or an image is required depends on that template. The fileID/ossPath pairing and the account-must-match-the-file constraint are echoed from the schema rather than extended, so this is above baseline but not exhaustive.

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 (generate a video from a hailuoai.video agent template) and immediately scopes it against the sibling minimax_create_video, which is called out as the free-form alternative. It also pins down the source of templateId (minimax_list_agent_templates) and the endpoint, so the agent can tell exactly which tool this is.

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?

Explicitly says free-form generation is minimax_create_video, which is the key when-not-to-use signal, and instructs the agent to check the template's prompt/image requirements via minimax_list_agent_templates. It also notes the operation draws on the account's MiniMax credits, which is a prerequisite-cost signal an agent can weigh before calling.

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