RunAPI Midjourney MCP Server

image_to_video

Convert a source image into a Midjourney video task on RunAPI, returning a task ID, status, and output URLs.

Instructions

Create a Midjourney task on RunAPI (image to video). Returns a task id, status, and output URLs.

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": {
      "source_image_url": "<source_image_url>"
    },
    "name": "image_to_video"
  }
}

Input Schema

Name	Required	Description
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	No	Declared type: string.
`timeout_ms`	No
`enable_loop`	No	Declared type: boolean.
`callback_url`	No	Declared type: string.
`poll_interval_ms`	No
`source_image_url`	Yes	Declared type: string.
`output_resolution`	No	Declared type: string. Known values: "480p".
`last_frame_image_url`	No	Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.4.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / enable_loop / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / last_frame_image_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "midjourney-image-to-video"
-]
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string. Known values: \"480p\"."
```
- removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "480p"
-]
```
- addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / source_image_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
First observedv0.3.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does add real value by disclosing the return shape (task id, status, output URLs) despite there being no output schema, and it identifies the external RunAPI service. However it omits cost, async/polling behavior, permission needs, and what happens on timeout or failure.

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?

Two tight sentences, front-loaded with the action and service, with the return contract last. No filler or redundancy.

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 10-parameter creation tool with no annotations and no output schema, the description is thin: it says nothing about the wait/poll to terminal status, timeout_ms, poll_interval_ms, callback_url, or model slug selection, all of which materially affect invocation. Only the return payload is covered.

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 80%, so the schema largely documents the parameters itself. The description adds no parameter-level meaning beyond implying a source image; the 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.

Purpose4/5

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

States a specific verb and resource ('Create a Midjourney task ... image to video') and names the backing service (RunAPI). The parenthetical scopes it to the image-to-video transform, which distinguishes it from text_to_image and extend_video among siblings, though it does not name those alternatives directly.

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 statement of when to use this tool versus its siblings (extend_video, text_to_image, edit_image) or versus get_task for polling. The '(image to video)' hint implies a use case but gives no explicit selection criteria or prerequisites.

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

Deploy Server