Qwen 2 MCP Server

edit_image

Modify an image using Qwen 2 by providing a prompt and source image URL, then receive a task ID, status, and output URLs.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`seed`	No	Declared type: integer.
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	Yes	Declared type: string.
`timeout_ms`	No
`aspect_ratio`	No	Declared type: string. Known values: "1:1", "2:3", "3:2", "3:4", "4:3", "9:16", "16:9", "21:9".
`callback_url`	No	Declared type: string.
`output_format`	No	Declared type: string. Known values: "jpeg", "png".
`poll_interval_ms`	No
`source_image_url`	Yes	Declared type: string.
`enable_safety_checker`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.2.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / aspect_ratio / description
```
Added value: +"Declared type: string. Known values: \"1:1\", \"2:3\", \"3:2\", \"3:4\", \"4:3\", \"9:16\", \"16:9\", \"21:9\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "1:1",
-  "2:3",
-  "3:2",
-  "3:4",
-  "4:3",
-  "9:16",
-  "16:9",
-  "21:9"
-]
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / enable_safety_checker / description
```
Added value: +"Declared type: boolean."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "qwen-2-edit-image"
-]
```
- addedInput schema / properties / output_format / description
```
Added value: +"Declared type: string. Known values: \"jpeg\", \"png\"."
```
- removedInput schema / properties / output_format / enum
```
Removed value: -[
-  "jpeg",
-  "png"
-]
```
- addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / seed / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / seed / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / source_image_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed6 schema fields changedv0.1.7Aug 5, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / enable_safety_checker
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / prompt / type
```
Added value: +"string"
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_image_url / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[
+  "prompt",
+  "source_image_url"
+]
```
First observedv0.1.0Jun 24, 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 bears the full burden. It does add useful context by disclosing the asynchronous task model and the return shape (task id, status, output URLs), but it omits auth requirements, cost/pricing implications, rate limits, and what happens if the task times out.

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 tight sentences with the core action front-loaded and the return values stated second. No filler, though the parenthetical '(edit image)' is slightly awkwardly placed.

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

Completeness3/5

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

For an 11-parameter task-creation tool with no output schema, the description covers the basic return shape but leaves the async lifecycle (polling vs callback_url, timeout behavior) and operational constraints unexplained. Adequate but with clear gaps.

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 high-coverage threshold, so the schema already documents parameters like wait, model, aspect_ratio, and output_format. The description adds no parameter meaning beyond that baseline.

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 action and resource: creating a Qwen 2 RunAPI task that edits an image. It is clear what the tool does, but it does not distinguish itself from sibling text_to_image or explain why one would pick image editing over generation.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as text_to_image or get_task for retrieving results. The only hint of workflow is the 'wait' parameter defaulting to polling, which lives in the schema, not the description.

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

Deploy Server

edit_image

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools