RunAPI Midjourney MCP Server

get_seed

Retrieve the seed value for a Midjourney image by providing its image ID, enabling reproducible image generation.

Instructions

Run a synchronous Midjourney operation on RunAPI (get seed). 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": {
      "image_id": "<image_id>"
    },
    "name": "get_seed"
  }
}

Input Schema

Name	Required	Description	Default
`image_id`	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 / image_id / 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, the description carries the full behavioral burden. It discloses that the call is synchronous and returns the operation result, which is useful against async siblings, but says nothing about auth requirements, cost/pricing implications, failure modes, or what 'the operation result' actually contains.

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 operation type. The second sentence ('Returns the operation result') is nearly filler but the overall size is appropriate and wastes little space.

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 single-parameter operation with no output schema, the description should clarify what a seed return value is and how it is presented. 'Returns the operation result' is too vague to tell an agent what it will receive or how to use it.

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 image_id parameter, so the structured field already documents the input; the description adds no meaning about the image reference or its format. Baseline 3 applies when the schema does the heavy lifting.

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: 'Run a synchronous Midjourney operation on RunAPI (get seed).' It never explains what a seed is or what retrieving it accomplishes, and does not differentiate this from siblings like image_to_prompt or get_task, which also touch Midjourney artifacts.

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 guidance on when to use this tool versus alternatives such as get_task (also waits on an operation) or image_to_prompt. The word 'synchronous' hints at a blocking call but no condition or exclusion is stated.

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

Deploy Server