Skip to main content
Glama

midjourney_get_tasks_batch

Retrieve status and results for multiple Midjourney generation tasks in a single request. Use for batch tracking or paginated listing of recent tasks.

Instructions

Query multiple Midjourney generation tasks at once.

Efficiently check the status of multiple tasks in a single request.
More efficient than calling midjourney_get_task multiple times.

Use this when:
- You have multiple pending generations to check
- You want to get status of several images/videos at once
- You're tracking a batch of generations
- You want to list recent tasks with pagination (omit task_ids and trace_ids)

Returns:
    Status and result information for all queried tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idsNoList of task IDs to query. Maximum recommended batch size is 50 tasks.
trace_idsNoList of trace IDs to query. Used as an alternative to task_ids.
offsetNoOffset for pagination when retrieving a batch of tasks. Default is 0.
limitNoMaximum number of tasks to return in a batch. Default is 12.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the query behavior, mentions pagination, and max batch size in schema, but does not disclose rate limits, authentication needs, or behavior for invalid IDs. Adequate but not exhaustive.

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?

The description is very concise, with a clear header and bullet-pointed usage scenarios. Every sentence adds value, no fluff or repetition.

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?

Given the tool's complexity (4 parameters, 0 required, high schema coverage, and output schema), the description covers purpose, usage, return value ('Status and result information'), and pagination. No significant gaps remain.

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 description coverage is 100%, so parameters are well-documented. The description adds value by explaining when to omit task_ids/trace_ids for pagination, and the schema includes max batch recommendation. This goes beyond baseline 3.

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 it queries multiple Midjourney tasks at once, specifying action (query), resource (tasks), and batching. It distinguishes itself from the sibling tool midjourney_get_task by emphasizing efficiency and batch capability.

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?

The description explicitly lists four use cases with bullet points, guiding when to use this tool (multiple pending checks, batch status, pagination). It implies alternatives (single task queries use midjourney_get_task) without explicitly naming it, but the context is clear.

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/MidjourneyMCP'

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