Skip to main content
Glama

midjourney_blend

Blend 2-5 images into a new creative fusion using Midjourney. Define how images combine with an optional prompt and choose generation mode.

Instructions

Blend multiple images together using Midjourney.

This allows you to combine 2-5 images into a new creative fusion.

Use this when:
- You want to merge elements from multiple images
- You want to create composite images
- You want to blend styles or subjects together

Example:
- Blend a bear image with a chainsaw image with prompt "The bear is holding the chainsaw"

Returns:
    Task ID and blended image information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_urlsYesList of image URLs to blend together. Supports 2-5 images. Images should be pure image URLs (not web pages containing images).
promptNoDescription of how to blend the images. Examples: 'The bear is holding the chainsaw', 'Combine the face with the background'
modeNoGeneration mode.fast

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states that it blends images and returns a Task ID, implying asynchronous generation. It does not disclose side effects, resource consumption, authentication needs, or other behavioral traits, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with a clear structure: purpose, usage list, example, and return type. It is front-loaded with the main action. Some redundancy exists (e.g., repeating 'blend' and 'combine'), but overall it's well-organized and no extraneous 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 presence of an output schema and comprehensive parameter documentation, the description covers the tool's purpose, usage scenarios, and return value. It could be more complete by mentioning limitations like image size or format, but it sufficiently sets expectations for a blending 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 coverage is 100%, providing full parameter descriptions. The tool description adds an example but does not provide additional semantics beyond the schema. With high schema coverage, the baseline of 3 is appropriate for not adding extra value.

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 blends multiple images (2-5) using Midjourney, which is a specific verb+resource. It distinguishes from siblings like midjourney_imagine (text-to-image) by focusing on image blending, though it doesn't explicitly name alternative tools.

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 description provides explicit 'Use this when' bullet points covering merging, composite creation, and style blending. It gives clear context but does not mention when not to use or suggest alternative tools among the siblings, which would improve guidance.

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