seedream-mcp

edit_image

Submit an image-editing task to RunAPI using source image URLs; returns task ID, status, and output URLs for tracking results.

Instructions

Create a Seedream 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`	No	Declared type: string.
`timeout_ms`	No
`aspect_ratio`	No	Declared type: string. Known values: "1:1", "4:3", "3:4", "16:9", "9:16", "2:3", "3:2", "21:9".
`callback_url`	No	Declared type: string.
`output_count`	No	Declared type: integer.
`output_format`	No	Declared type: string.
`output_quality`	No	Declared type: string.
`poll_interval_ms`	No
`output_resolution`	No	Declared type: string.
`source_image_urls`	Yes	Declared type: array.
`enable_safety_checker`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv0.2.0Oct 2, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / aspect_ratio / description
```
Added value: +"Declared type: string. Known values: \"1:1\", \"4:3\", \"3:4\", \"16:9\", \"9:16\", \"2:3\", \"3:2\", \"21:9\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "1:1",
-  "4:3",
-  "3:4",
-  "16:9",
-  "9:16",
-  "2:3",
-  "3:2",
-  "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: -[
-  "seedream-4.5-edit",
-  "seedream-5-lite-edit",
-  "seedream-5-pro-edit",
-  "seedream-v4-edit"
-]
```
- addedInput schema / properties / output_count / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / output_count / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / output_format / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / output_quality / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string."
```
- 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_urls / description
```
Added value: +"Declared type: array."
```
- removedInput schema / properties / source_image_urls / maxItems
```
Removed value: -14
```
- removedInput schema / properties / source_image_urls / minItems
```
Removed value: -1
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed14 schema fields changedv0.1.7Jul 22, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / enable_safety_checker
```
Added value: +{
+  "type": "boolean"
+}
```
- changedInput schema / properties / model / enum
```
Previous value: -[
-  "seedream-4.5-edit",
-  "seedream-5-lite-edit",
-  "seedream-v4-edit"
-]New value: +[
+  "seedream-4.5-edit",
+  "seedream-5-lite-edit",
+  "seedream-5-pro-edit",
+  "seedream-v4-edit"
+]
```
- removedInput schema / properties / output_count / enum
```
Removed value: -[
-  1,
-  2,
-  3,
-  4,
-  5,
-  6
-]
```
- addedInput schema / properties / output_format
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / output_quality / enum
```
Removed value: -[
-  "basic",
-  "high"
-]
```
- removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "1k",
-  "2k",
-  "4k"
-]
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_image_urls / items
```
Added value: +{}
```
- addedInput schema / properties / source_image_urls / maxItems
```
Added value: +14
```
- 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: +[
+  "source_image_urls"
+]
```
First observedv0.1.0Jun 23, 2026

TDQS

B3.1/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, and it does disclose that the call is asynchronous and returns a task id, status, and output URLs. It omits polling/terminal-status behavior implied by the wait parameter, authentication or cost implications, and the effect of enable_safety_checker.

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 the action front-loaded and zero filler. The size is tight, though the brevity contributes to the missing operational context rather than being purely optimal.

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 14-parameter tool with no annotations and no output schema, the description is thin: it never explains the wait/polling contract, how source_image_urls and prompt combine, or which parameters are essential. It names return fields, which is the one thing output-schema absence makes valuable, but leaves most operational requirements unstated.

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 86%, so the schema already documents parameters such as wait, model, and aspect_ratio. The description adds no parameter-level meaning at all, so the baseline 3 applies.

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 Seedream task on RunAPI') and tags the mode with '(edit image)', which separates it from the sibling text_to_image. The framing as task creation rather than an image-editing action is slightly indirect, but an agent can identify what it does.

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 guidance on when to pick this over text_to_image, nor any mention of the async pattern (wait defaults to true; set it false and poll with get_task). The sibling get_task exists precisely for the non-waiting path and the description never routes the agent there.

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