Skip to main content
Glama
tengmmvp

Seedream 4.0 MCP

by tengmmvp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

seedream_text_to_image

Generate a single high-quality image from a text description by providing clear and accurate instructions.

Instructions

文生图：

通过给模型提供清晰准确的文字指令，即可快速获得符合描述的高质量单张图片。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.2.6
    • addedInput schema / $defs / GenerationTool
      Added value: +{
+  "additionalProperties": false,
+  "description": "模型工具配置。",
+  "properties": {
+    "type": {
+      "$ref": "#/$defs/GenerationToolType",
+      "description": "工具类型，目前仅支持 web_search。"
+    }
+  },
+  "required": [
+    "type"
+  ],
+  "title": "GenerationTool",
+  "type": "object"
+}
    • addedInput schema / $defs / GenerationToolType
      Added value: +{
+  "description": "模型工具类型枚举",
+  "enum": [
+    "web_search"
+  ],
+  "title": "GenerationToolType",
+  "type": "string"
+}
    • changedInput schema / $defs / OptimizePromptOptions / description
      Previous value: -"提示词优化配置模型。\n\n配置提示词优化策略，平衡生成质量与响应速度。"New value: +"提示词优化配置模型\n\n配置提示词优化策略，平衡生成质量与响应速度。"
    • addedInput schema / $defs / OutputFormat
      Added value: +{
+  "description": "图片文件输出格式枚举",
+  "enum": [
+    "jpeg",
+    "png"
+  ],
+  "title": "OutputFormat",
+  "type": "string"
+}
    • changedInput schema / $defs / ResponseFormat / description
      Previous value: -"图片生成响应格式枚举。\n\n定义生成结果的返回格式，支持 URL 链接和 Base64 编码两种方式。"New value: +"图片生成响应格式枚举"
    • addedInput schema / $defs / TextToImageInput / properties / output_format
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/OutputFormat"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "输出图片格式，仅 doubao-seedream-5.0 支持 jpeg 或 png。"
+}
    • addedInput schema / $defs / TextToImageInput / properties / parallelism
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 4,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "并行度上限；未提供时自动使用 min(request_count, 4)。",
+  "title": "Parallelism"
+}
    • addedInput schema / $defs / TextToImageInput / properties / request_count
      Added value: +{
+  "default": 1,
+  "description": "并行请求次数，1 表示单次请求；可用于一次发起多次生成以减少等待。",
+  "maximum": 4,
+  "minimum": 1,
+  "title": "Request Count",
+  "type": "integer"
+}
    • changedInput schema / $defs / TextToImageInput / properties / size / description
      Previous value: -"生成图片尺寸，可选 1K/2K/4K；未提供时使用全局默认值。"New value: +"生成图片尺寸，可选 1K/2K/3K/4K 或 <宽>x<高> 像素值；未提供时使用全局默认值。"
    • addedInput schema / $defs / TextToImageInput / properties / tools
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/GenerationTool"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "模型工具配置，仅 doubao-seedream-5.0 支持，目前仅支持 web_search。",
+  "title": "Tools"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "Annotations": {
-      "additionalProperties": true,
-      "properties": {
-        "audience": {
-          "anyOf": [
-            {
-              "items": {
-                "enum": [
-                  "user",
-                  "assistant"
-                ],
-                "type": "string"
-              },
-              "type": "array"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "title": "Audience"
-        },
-        "priority": {
-          "anyOf": [
-            {
-              "maximum": 1,
-              "minimum": 0,
-              "type": "number"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "title": "Priority"
-        }
-      },
-      "title": "Annotations",
-      "type": "object"
-    },
-    "TextContent": {
-      "additionalProperties": true,
-      "description": "Text content for a message.",
-      "properties": {
-        "_meta": {
-          "anyOf": [
-            {
-              "additionalProperties": true,
-              "type": "object"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "title": "Meta"
-        },
-        "annotations": {
-          "anyOf": [
-            {
-              "$ref": "#/$defs/Annotations"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null
-        },
-        "text": {
-          "title": "Text",
-          "type": "string"
-        },
-        "type": {
-          "const": "text",
-          "title": "Type",
-          "type": "string"
-        }
-      },
-      "required": [
-        "type",
-        "text"
-      ],
-      "title": "TextContent",
-      "type": "object"
-    }
-  },
-  "properties": {
-    "result": {
-      "items": {
-        "$ref": "#/$defs/TextContent"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "seedream_text_to_imageOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations are minimal (readOnlyHint false, etc.). Description adds only 'quickly obtain' and 'high-quality', lacking behavioral details like cost, rate limits, or side effects. The agent may not know if generation is expensive or time-consuming.

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?

Single sentence, no wasted words, front-loaded with core purpose. Could be more detailed without sacrificing conciseness, but it is efficiently structured.

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?

Despite having many parameters and sibling tools, the description is too brief. It lacks output details, parameter constraints, and usage context, making it insufficient for complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% – description does not explain any parameters. The schema itself has descriptions for each property, but the description fails to compensate for the low coverage, offering no added meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the verb (文生图 = text-to-image) and resource (single high-quality image from text). It distinguishes from sibling tools like image_to_image or multi_image_fusion by emphasizing text input and single image output.

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 use this tool versus alternatives. Does not mention when not to use it or provide context for selecting between siblings.

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

Deploy Server

Other Tools