Skip to main content
Glama
Sign In
Midjourney MCP Server

Midjourney MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

midjourney_type

Types text into a specified numbered field on the current Midjourney page, using the field number from the last read to enter prompts or form values.

Instructions

Type text into a numbered field on the current Midjourney page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "midjourney_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, and it omits the behaviors that matter most for a UI-typing tool: whether typing submits the form (Enter key), whether existing field content is replaced or appended, and what happens if the field number is stale or invalid. It establishes only that text goes into a numbered field.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently written, though its brevity contributes to the missing behavioral detail rather than compensating for it.

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

Completeness2/5

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

For a stateful browser-automation tool with no annotations and no output schema, the definition should say that a page must be open, that 'element' refers to the last midjourney_read result, and whether typing triggers a submit. None of that stateful sequencing or post-condition information is present.

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 description coverage is 100%, with 'element' documented as 'Field number from the last read' and 'text' as the literal string, so the schema already does the semantic work. The description adds no additional meaning about formats, limits, or how element numbering is derived beyond the schema's own note.

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 states a specific verb ('Type text') and target ('a numbered field on the current Midjourney page'), which is enough to distinguish it from midjourney_click or midjourney_read. It does not explicitly name a sibling it replaces or excludes, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no mention of alternatives such as midjourney_click for non-text interactions. The phrase 'current ... page' only weakly implies a page must already be open, leaving the agent to infer prerequisites from the sibling list.

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