Skip to main content
Glama

midjourney_imagine

Generate AI images from text prompts, delivering a 2x2 grid of four variations for visualization and creative illustration.

Instructions

Generate AI images from a text prompt using Midjourney.

This is the primary way to create images - describe what you want and Midjourney
will generate a 2x2 grid of 4 image variations.

Use this when:
- You want to create new images from a text description
- You have a creative vision to visualize
- You need AI-generated artwork or illustrations

For image transformations like upscaling or variations, use midjourney_transform instead.

Returns:
    Task ID and generated image information including URLs, dimensions, and available actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hdNoEnable 2K HD output. V8.1 uses separate SD and HD resolution-based rates; V8.0 Alpha uses different premium rules.
modeNoGeneration mode. 'fast' is recommended and 'relax' is slower but cheaper. 'turbo' is faster on supported versions, but V8.1 only supports fast and relax.fast
promptYesDescription of the image to generate. Be descriptive about style, subject, lighting, and composition. Examples: 'A majestic lion in a savanna at sunset, cinematic lighting', 'Cyberpunk city street at night, neon lights, rain, photorealistic', 'Abstract watercolor painting of mountains and clouds'
qualityNoImage quality level for versions that support --quality / --q. This parameter is not supported in V8.1; use hd for higher-resolution V8.1 output.
timeoutNoTimeout in seconds for the API to return data. Default is 480.
versionNoMidjourney model version to use, e.g. '8.1', '8', '7', '6.1'. '8.1' is the latest version and is recommended. Leave unset to use Midjourney's default.
moodboardNoWhether the prompt uses a moodboard. V8.1 bills it at the selected SD/HD resolution rate; V8.0 Alpha uses different premium rules.
translationNoIf true, automatically translate non-English prompts to English for better results.
callback_urlNoWebhook callback URL for asynchronous notifications. When provided, the API will call this URL when the image is generated.
split_imagesNoIf true, split the 2x2 grid result into 4 separate images returned via sub_image_urls.
style_referenceNoWhether the prompt includes --sref style reference. V8.1 bills it at the selected SD/HD resolution rate; V8.0 Alpha uses different premium rules.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the 2x2 grid output and return information including URLs and available actions, but does not mention asynchronous behavior, cost/credit implications, or that generation may take considerable time. These are important behavioral traits for an image-generation tool, so the description adds some value but leaves gaps.

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 well-structured with a clear opening sentence, a brief explanatory paragraph, a bulleted 'when to use' list, an alternative reference, and a 'Returns' section. Every sentence adds value, and it is concise without being sparse.

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 complexity (11 params, output schema present) the description adequately covers purpose, usage scenarios, and high-level returns. It is nearly complete for tool selection and invocation, but could optionally mention asynchronous task handling or how to use the returned Task ID to track progress, which would make it fully complete.

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?

All 11 parameters have detailed descriptions in the input schema, providing 100% coverage. The tool description itself does not add parameter semantics beyond what the schema already conveys, so the baseline score of 3 applies.

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 opens with 'Generate AI images from a text prompt using Midjourney,' a specific verb+resource statement. It then clarifies this is 'the primary way to create images' and distinguishes from midjourney_transform for transformations, making the tool's unique purpose clear.

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 'Use this when' scenarios (new images, creative vision, artwork) and provides an explicit alternative: 'For image transformations like upscaling or variations, use midjourney_transform instead.' This gives clear guidance on when to choose this tool over a key sibling.

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