RunAPI Midjourney MCP Server

shorten_prompt

Condense lengthy Midjourney prompts into shorter versions via RunAPI, returning the result for downstream image generation.

Instructions

Run a synchronous Midjourney operation on RunAPI (shorten prompt). Returns the operation result.

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": {
      "prompt": "<prompt>"
    },
    "name": "shorten_prompt"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.4.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
First observedv0.3.0Jul 29, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden, yet it only mentions synchronous execution and that a result is returned. It omits auth requirements, rate limits, whether the operation is billed, or what happens on failure — significant gaps for an API-backed operation.

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?

Two short sentences, front-loaded with the action. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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 an operation with no annotations and no output schema, the description should explain what the result looks like and any operational constraints. It says only that it returns 'the operation result', leaving the agent without enough to call it confidently.

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% for the single required 'prompt' parameter, so the schema does the documentation work and a baseline of 3 applies. The description adds no format, length, or content guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description largely restates the tool name ("shorten prompt") inside a generic wrapper phrase about running a Midjourney operation on RunAPI. It does not state what shortening a prompt means or how the result differs from siblings like image_to_prompt or text_to_image, so an agent gains little beyond the name itself.

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 indication of when to use this tool versus the many sibling image/prompt tools, no prerequisites, and no exclusions. The only implicit context is that it is a Midjourney operation, which is not enough to route selection.

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

Deploy Server