Skip to main content
Glama
Sign In
Midjourney MCP Server

Midjourney MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

midjourney_read

Reads the current Midjourney page, returning its text plus numbered buttons, links, and fields so AI agents can locate and act on the right interface elements.

Instructions

Read the current Midjourney page: its text and numbered buttons, links and fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "midjourney_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole burden. "Read" signals a non-mutating operation and it does name the returned artifacts, but it says nothing about truncation/limits on large pages, what happens when no page is open, or how the numbered buttons relate to midjourney_click (the key downstream behavior).

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?

One front-loaded sentence with no filler; the enumeration of page contents is the most useful information and appears immediately. Slightly terse for a tool that is the entry point to an interactive loop.

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

Completeness3/5

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

With no output schema, the description must convey return shape; it does so at a high level (text, numbered buttons, links, fields). It is nonetheless thin for a stateful page-read tool whose output drives subsequent click/type calls, leaving the agent to discover limits and failure modes by experiment.

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% and the single optional `element` parameter is fully documented in the schema as scoping the read to one element. The description never mentions `element` and adds no scoping syntax or semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ("Read the current Midjourney page") and enumerates what it exposes: text, numbered buttons, links and fields. That is enough to separate it from click/type/open siblings by implication, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "current Midjourney page" implies a page must already be open, but there is no explicit when-to-use guidance, no prerequisite stating that midjourney_open must run first, and no routing to alternatives such as midjourney_status.

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