Skip to main content
Glama

midjourney_imagine

Generate AI images by describing your vision in a text prompt, producing a 2x2 grid of four image variations for your creative projects.

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
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'
modeNoGeneration mode. 'fast' is recommended for most use cases. 'turbo' is faster but uses more credits. 'relax' is slower but cheaper.fast
translationNoIf true, automatically translate non-English prompts to English for better results.
split_imagesNoIf true, split the 2x2 grid result into 4 separate images returned via sub_image_urls.
timeoutNoTimeout in seconds for the API to return data. Default is 480.
callback_urlNoWebhook callback URL for asynchronous notifications. When provided, the API will call this URL when the image is generated.
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.
hdNoEnable HD mode (V8/V8.1). Generates higher resolution images at 4x cost.
qualityNoImage quality level. Values: '.25', '.5', '1', '2', '4'. Quality '4' is V8/V8.1 only.
style_referenceNoWhether the prompt includes --sref style reference. In V8 this incurs 4x cost.
moodboardNoWhether using moodboard feature (V8 only, multiple reference images). Incurs 4x cost.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description discloses key behaviors: generates a 2x2 grid, returns task ID and image info, explains mode cost implications, and mentions HD and style reference costs. No mention of authorization or destructive actions, but overall sufficient.

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?

Description is concise, well-structured with bullet points for usage, and front-loaded with the primary purpose. Every sentence adds value.

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 parameters, output schema exists), the description covers key aspects: main function, usage, alternative tool, and return info. Could mention asynchronous behavior or timeout more explicitly, but adequate.

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 baseline 3. The description adds minimal extra meaning beyond the schema; it repeats the prompt purpose but doesn't deepen understanding of each parameter.

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 generates AI images from text prompts using Midjourney, describes the output as a 2x2 grid, and differentiates from sibling tools like midjourney_transform.

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?

Explicit 'Use this when' bullet points and a direct reference to midjourney_transform for transformations provide clear guidance on when to use vs alternatives.

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