Skip to main content
Glama

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

List video templates

minimax_list_agent_templates
Read-onlyIdempotent

Browse hailuoai.video agent video templates for minimax_create_template_video: each template's id (the templateId), title and preview video. With templateId, one template's details instead: credits (the price its page shows), requirePrompt, requireImage, the prompt placeholder and inputs. Pages of limit items (default 30); pass the last id as lastId for the next page while hasNext is true. GET /videos/agent-templates.

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

Input Schema

NameRequiredDescriptionDefault
limitNoTemplates per page (default 30).
lastIdNoThe last template id of the previous page.
accountNoThe account id from minimax_list_accounts. Optional when you have one account, required with more.
templateIdNoA template id: returns that template's details and required inputs.

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 declare readOnly/idempotent/non-destructive, and the description adds real substance on top: the exact fields returned per template, the extra detail fields in templateId mode, and the pagination contract (default 30, hasNext loop). It does not cover error behavior or whether a missing templateId/account surfaces as empty results, so it stops short of a 5.

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?

Two dense sentences that front-load the browse mode and put the templateId variant immediately after, with pagination last. The telegraphic phrasing ("Pages of limit items (default 30); pass the last id as lastId") is efficient but slightly run-on, costing a little readability.

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 return-value burden and does so by enumerating the per-template fields and the detail fields. Pagination and the dual-mode contract are fully covered; only error/empty-case and account-disambiguation behavior 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: that templateId switches the response shape entirely, that credits is the displayed price, and that lastId is fed from the prior page's final id. It doesn't clarify account-selection behavior beyond what the schema already says.

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 ("Browse hailuoai.video agent video templates") and ties it to the consuming sibling minimax_create_template_video, plus names the alternate detail mode keyed on templateId. An agent can tell this apart from the list_* siblings and the create/get tools without opening the 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 clear conditional routing: omit templateId to browse, supply templateId to get one template's details, and use lastId with hasNext to page. It also implies the workflow (browse before creating a template video), but it never states exclusions or what to do instead when a template is unknown or when account is ambiguous.

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