Skip to main content
Glama

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

List videos

minimax_list_videos
Read-onlyIdempotent

List one account's videos on hailuoai.video, including running ones and those made in the web app: videoId, statusLabel, statusFinal, URLs and prompt (desc). Pages of limit items (default 30); pass the last videoId as lastVideoId for the next page while hasNext is true. Only what this API is tracking now: minimax_list_running_jobs. GET /videos.

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

Input Schema

NameRequiredDescriptionDefault
limitNoVideos per page (default 30).
accountNoThe account id from minimax_list_accounts. Optional when you have one account, required with more.
lastVideoIdNoThe last videoId of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds real value beyond that by disclosing inclusion of in-flight and web-app-created videos and by describing the hasNext pagination contract. It stops short of noting ordering, rate limits, or what happens at the end of the list, so it is useful but not rich.

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

Conciseness3/5

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

The core is front-loaded and dense: scope, returned fields, pagination, and account rule arrive in order with little filler. The dangling clause "Only what this API is tracking now: minimax_list_running_jobs" is a sentence fragment that costs space without conveying a usable rule, and the trailing "GET /videos" is redundant with the stated resource.

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 read-only list tool with no output schema, the description carries the necessary weight: it names the fields returned, explains the pagination loop and default page size, and states the account requirement. The one gap is that the relationship to minimax_list_running_jobs remains ambiguous, which matters because that is the closest sibling.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters are already documented in the schema, which sets the baseline at 3. The description contributes the pagination mechanics for lastVideoId (feed it the previous page's final videoId while hasNext is true) and repeats the default page size. That is helpful loop semantics but not additional per-parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("List one account's videos on hailuoai.video") and scopes it precisely: running videos plus web-app-created ones. It even enumerates the returned fields (videoId, statusLabel, statusFinal, URLs, prompt), which lets an agent distinguish it from get-style siblings. The only deduction is the garbled sibling reference "Only what this API is tracking now: minimax_list_running_jobs," which blurs rather than sharpens the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage for pagination is explicit and actionable: pass the last videoId as lastVideoId while hasNext is true. The account parameter's condition (optional with one account, required with more) is also spelled out. However, the guidance on when to choose this over minimax_list_running_jobs is implied by a fragmentary sentence rather than stated, so the alternative-selection rule is left to 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