seedream-mcp

text_to_image

Generate images from text prompts by creating Seedream tasks on RunAPI, returning task IDs, status, and output URLs for tracking and retrieval.

Instructions

Create a Seedream task on RunAPI (text to 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.
`enable_safety_checker`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 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-text-to-image",
-  "seedream-5-lite-text-to-image",
-  "seedream-5-pro-text-to-image",
-  "seedream-v4-text-to-image"
-]
```
- 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 / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / required
```
Added value: +[]
```
Addedv0.1.8Aug 5, 2026
Removedv0.1.7Jul 22, 2026
First observedv0.1.0Jun 23, 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, and it does disclose that this is an asynchronous task creation returning a task id, status, and output URLs. However, it omits the default polling behavior implied by the wait parameter, any cost/credit implications (notable given the check_pricing sibling), and failure modes. Some value added, but significant gaps remain for a 13-parameter task-creation tool.

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 action front-loaded and the return values stated second. Nothing is wasted, though the parenthetical '(text to image)' slightly duplicates the tool name.

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 a 13-parameter, zero-required, async task tool with no annotations and no output schema, the description covers purpose and return shape but leaves out cost, authentication needs, and how the wait/poll defaults behave. Adequate for a basic call, but not complete for the tool's complexity.

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 high (85%), so the schema already documents most inputs; the description adds no parameter-level detail such as prompt syntax, effect of output_count, or the wait/polling interaction. Baseline 3 is appropriate when the schema does the heavy lifting and the description contributes nothing extra.

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 clarifies the modality with '(text to image)', which distinguishes it from the edit_image sibling. It stops short of explicitly naming when this tool is preferred over edit_image or decompose_layers, but the purpose is unambiguous.

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 prerequisites (API key/login), and no routing to alternatives such as edit_image for modifying existing images. The agent must infer usage entirely from the tool name and 'text to image' parenthetical.

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

Deploy Server

text_to_image

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools