Skip to main content
Glama

midjourney_get_task

Query the status and retrieve results from a Midjourney generation task, including image/video URLs and metadata.

Instructions

Query the status and result of a Midjourney generation task.

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

Use this when:
- You want to check if a generation has completed
- You need to retrieve URLs from a previous generation
- You want to get the full details of a generated image or video
- You used async callback and want to check results later

Returns:
    Task status and generation result including URLs, dimensions, and available actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idNoThe task ID returned from a generation request. This is the 'task_id' field from any midjourney_imagine, midjourney_describe, midjourney_edit, or midjourney_generate_video tool response.
trace_idNoThe trace ID to retrieve. Used as an alternative to task_id for identifying a task.

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 bears the full burden. It states the tool queries and retrieves but does not disclose any potential side effects, rate limits, or idempotency. For a query tool, this is adequate but lacks depth on constraints or error states.

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 extremely concise: a single sentence for purpose, a bulleted list of usage scenarios, and a returns summary. Every sentence adds value with no redundancy.

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?

Given the presence of an output schema and full parameter descriptions, the description covers purpose, usage, and key return fields (URLs, dimensions, actions). It lacks mention of idempotency or multiplicity but is complete for a simple query tool.

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 description coverage is 100%, with both parameters (task_id, trace_id) already well-described in the schema. The tool description adds no new meaning beyond summarizing their purpose. Baseline of 3 is appropriate.

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 the status and result of a Midjourney generation task. It specifies retrieving image/video URLs and metadata, and distinguishes this from siblings like midjourney_imagine (creation) and midjourney_get_tasks_batch (batch query).

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?

Four explicit 'Use this when' scenarios are provided (check completion, retrieve URLs, get full details, async results). It does not mention when not to use it or direct alternatives, 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