Skip to main content
Glama
AceDataCloud

MidjourneyMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

midjourney_describe

Analyze any image to get 4 AI-generated text descriptions that work as Midjourney prompts, helping you reverse-engineer style, composition, and aspect ratio.

Instructions

Get AI-generated descriptions of an image.

This analyzes an image and returns 4 alternative text descriptions that
could be used as prompts to recreate similar images with Midjourney.

Use this when:
- You want to understand what prompts might create a similar image
- You want to reverse-engineer an image's style or composition
- You need inspiration for prompts based on existing artwork
- You want to describe an image for documentation

The descriptions include style tags and aspect ratio parameters that
Midjourney understands.

Returns:
    Four alternative descriptions of the image with Midjourney-compatible formatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_urlYesURL of the image to describe. Must be a direct image URL (JPEG, PNG, GIF, etc.), not a web page containing an image.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5
  2. Removedv0.1.4
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description bears full burden. It discloses the tool analyzes an image and returns descriptions with style tags. No side effects are mentioned, but the read-only nature is implied. Could explicitly state non-destructive behavior.

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 well-structured with a summary, bullet-point usage, and output note. Every sentence adds value, no unnecessary repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and an output schema, the description covers purpose, usage, and return format completely. No gaps.

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% with a clear description for image_url (must be direct URL). The tool description adds no additional parameter guidance, so baseline 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 the tool provides AI-generated descriptions of an image, returning 4 alternative text prompts. This distinguishes it from sibling tools like midjourney_imagine (generation) and midjourney_transform (editing).

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 lists specific use cases (e.g., reverse-engineering style, inspiration) but does not explicitly state when not to use or compare to alternatives. Still provides clear context for appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools