Skip to main content
Glama

midjourney_transform

Transform Midjourney images by upscaling, creating variations, zooming, or panning. Modify existing generations with actions like upscale, variation, zoom, and pan.

Instructions

Transform an existing Midjourney image with various operations.

This allows you to upscale, create variations, zoom, or pan existing images
generated by Midjourney.

Use this when:
- You want to upscale one of the 4 images from a generation
- You want to create variations of a specific image
- You want to zoom out or pan an image
- You want to regenerate with the same prompt

Workflow example:
1. Generate with midjourney_imagine -> get image_id
2. Upscale favorite: midjourney_transform(image_id, "upscale2")
3. Further upscale: midjourney_transform(new_image_id, "upscale_4x")

Returns:
    Task ID and transformed image information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_idYesID of the image to transform. This is the 'image_id' field from a previous generation result.
actionYesTransformation action to perform. Options include: - upscale1/2/3/4: Upscale one of the 4 images (top-left=1, top-right=2, bottom-left=3, bottom-right=4) - upscale_2x/4x: Further upscale an already upscaled image by 2x or 4x - variation1/2/3/4: Create variations of one of the 4 images - variation_subtle/strong: Create subtle or strong variations after upscaling - reroll: Regenerate all 4 images with the same prompt - zoom_out_2x/1_5x: Zoom out the image by 2x or 1.5x - pan_left/right/up/down: Pan the image in a direction
promptNoOptional prompt for the transformation. Used with variation_region action.
maskNoBase64-encoded mask image for variation_region action. White areas indicate regions to regenerate.
modeNoGeneration mode for the transformation.fast

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 describes actions and their effects, but lacks details on side effects, rate limits, or prerequisites like image_id validity. 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 well-structured: a brief purpose statement, bullet points for usage, a workflow example, and return info. No unnecessary words; efficiently conveys needed information.

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 tool's complexity (5 parameters, many actions) and existence of an output schema, the description covers main usage scenarios and workflow. Could improve by noting error handling or prerequisites.

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 coverage is 100%, and the description adds context: image_id is tied to a previous generation, prompt/mask are used with variation_region, and the workflow example explains action sequence. Adds value beyond 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 clearly states the tool transforms existing Midjourney images with operations like upscaling, variations, zoom, and pan. It distinguishes itself from generation tools but does not explicitly differentiate from midjourney_edit or midjourney_blend.

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?

The 'Use this when' section lists specific scenarios (upscale, variation, zoom, pan, reroll), and a workflow example is provided. However, it does not explicitly state when not to use this tool or mention alternatives like blend or edit.

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