@runapi.ai/flux-2-mcp

Official

by runapi-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

remix_image

Transform source images using a Flux 2 prompt on RunAPI; returns task ID, status, and output URLs.

Instructions

Create a Flux 2 task on RunAPI (remix image). Returns a task id, status, and output URLs.

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`	Yes	Image editing instruction. Declared type: string.
`timeout_ms`	No
`aspect_ratio`	No	Output aspect ratio. Declared type: string. Known values: "1:1", "4:3", "3:4", "16:9", "9:16", "3:2", "2:3", "auto".
`callback_url`	No	Webhook URL for async notifications. Declared type: string.
`output_count`	No	Number of images to generate. Declared type: integer. Known values: 1.
`poll_interval_ms`	No
`output_resolution`	No	Output resolution. Declared type: string. Known values: "1k", "2k".
`source_image_urls`	Yes	Public source image URLs. Declared type: array.
`enable_safety_checker`	No	Enable the safety checker. Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv0.3.0Oct 7, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedInput schema / properties / aspect_ratio / description

Previous value: -"Output aspect ratio."New value: +"Output aspect ratio. Declared type: string. Known values: \"1:1\", \"4:3\", \"3:4\", \"16:9\", \"9:16\", \"3:2\", \"2:3\", \"auto\"."

removedInput schema / properties / aspect_ratio / enum

Removed value: -[
-  "1:1",
-  "4:3",
-  "3:4",
-  "16:9",
-  "9:16",
-  "3:2",
-  "2:3",
-  "auto"
-]

changedInput schema / properties / callback_url / description

Previous value: -"Webhook URL for async notifications."New value: +"Webhook URL for async notifications. Declared type: string."

changedInput schema / properties / enable_safety_checker / description

Previous value: -"Enable the safety checker."New value: +"Enable the safety checker. Declared type: boolean."

removedInput schema / properties / model / enum

Removed value: -[
-  "flux-2-flex-remix-image",
-  "flux-2-max-remix-image",
-  "flux-2-pro-remix-image"
-]

changedInput schema / properties / output_count / description

Previous value: -"Number of images to generate."New value: +"Number of images to generate. Declared type: integer. Known values: 1."

removedInput schema / properties / output_count / enum
```
Removed value: -[
-  1
-]
```
changedInput schema / properties / output_count / type
```
Previous value: -"number"New value: +"integer"
```

changedInput schema / properties / output_resolution / description

Previous value: -"Output resolution."New value: +"Output resolution. Declared type: string. Known values: \"1k\", \"2k\"."

removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "1k",
-  "2k"
-]
```
addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```

changedInput schema / properties / prompt / description

Previous value: -"Image editing instruction."New value: +"Image editing instruction. Declared type: string."

removedInput schema / properties / prompt / maxLength
```
Removed value: -5000
```
removedInput schema / properties / prompt / minLength
```
Removed value: -3
```

changedInput schema / properties / source_image_urls / description

Previous value: -"Public source image URLs."New value: +"Public source image URLs. Declared type: array."

removedInput schema / properties / source_image_urls / maxItems
```
Removed value: -8
```
removedInput schema / properties / source_image_urls / minItems
```
Removed value: -1
```
addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```

Changed16 schema fields changedv0.2.1Jul 31, 2026
- addedInput schema / properties / aspect_ratio / description
```
Added value: +"Output aspect ratio."
```
- addedInput schema / properties / callback_url
```
Added value: +{
+  "description": "Webhook URL for async notifications.",
+  "type": "string"
+}
```
- addedInput schema / properties / enable_safety_checker
```
Added value: +{
+  "description": "Enable the safety checker.",
+  "type": "boolean"
+}
```
- changedInput schema / properties / model / enum
```
Previous value: -[
-  "flux-2-flex-remix-image",
-  "flux-2-pro-remix-image"
-]New value: +[
+  "flux-2-flex-remix-image",
+  "flux-2-max-remix-image",
+  "flux-2-pro-remix-image"
+]
```
- addedInput schema / properties / output_count
```
Added value: +{
+  "description": "Number of images to generate.",
+  "enum": [
+    1
+  ],
+  "type": "number"
+}
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Output resolution."
```
- addedInput schema / properties / prompt / description
```
Added value: +"Image editing instruction."
```
- addedInput schema / properties / prompt / maxLength
```
Added value: +5000
```
- addedInput schema / properties / prompt / minLength
```
Added value: +3
```
- addedInput schema / properties / prompt / type
```
Added value: +"string"
```
- addedInput schema / properties / source_image_urls / description
```
Added value: +"Public source image URLs."
```
- addedInput schema / properties / source_image_urls / items
```
Added value: +{}
```
- addedInput schema / properties / source_image_urls / maxItems
```
Added value: +8
```
- addedInput schema / properties / source_image_urls / minItems
```
Added value: +1
```
- addedInput schema / properties / source_image_urls / type
```
Added value: +"array"
```
- addedInput schema / required
```
Added value: +[
+  "prompt",
+  "source_image_urls"
+]
```
First observedv0.1.0Jun 23, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the async task model and return shape ('task id, status, and output URLs'), which is genuinely useful, but it omits authentication needs, cost implications, polling/timeout behavior tied to the wait parameter, and whether the operation is billable or destructive. For a paid async generation endpoint this is a significant gap.

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 with no filler, and the core purpose plus return shape are front-loaded. It is efficient, though arguably too terse for an 11-parameter asynchronous tool.

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?

With 11 parameters, no annotations, and no output schema, the description is thin. It covers only the high-level action and the return fields; it leaves out sibling differentiation, the wait/polling vs callback_url distinction, timeout expectations, and cost/auth context that an agent needs to invoke this paid async endpoint correctly.

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 82%, above the 80% threshold, so the schema already documents most parameters (prompt, source_image_urls, aspect_ratio, callback_url, etc.). The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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

Purpose3/5

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

The description gives a specific verb and resource ('Create a Flux 2 task on RunAPI') and the parenthetical '(remix image)' hints at image-to-image editing. However, it does not distinguish this from the sibling text_to_image — nothing states that this operates on existing source images rather than generating from scratch. An agent must infer the difference from the name and schema.

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 or when-not-to-use guidance, no mention of the alternative text_to_image, and no prerequisites (auth, credits, public source image requirement). The agent is given no routing signal beyond the tool name.

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

Deploy Server

remix_image

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools