Skip to main content
Glama
tengmmvp

Seedream 4.0 MCP

by tengmmvp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

seedream_multi_image_fusion

Fuse multiple reference images with a text prompt to create a unified image that merges styles, elements, and subjects from each source.

Instructions

多图融合：

根据输入的文本描述和多张参考图片，融合它们的风格、元素等特征来生成新图像。如衣裤鞋帽与模特图融合成穿搭图，人物与风景融合为人物风景图等。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 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 / MultiImageFusionInput / properties / image / description
      Previous value: -"参与融合的图片列表，支持 URL、本地路径，数量2-5张。"New value: +"图片列表，支持 URL、本地路径，数量2-14张。"
    • changedInput schema / $defs / MultiImageFusionInput / properties / image / maxItems
      Previous value: -5New value: +14
    • addedInput schema / $defs / MultiImageFusionInput / properties / output_format
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/OutputFormat"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "输出图片格式，仅 doubao-seedream-5.0 支持 jpeg 或 png。"
+}
    • addedInput schema / $defs / MultiImageFusionInput / 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 / MultiImageFusionInput / properties / request_count
      Added value: +{
+  "default": 1,
+  "description": "并行请求次数，1 表示单次请求；可用于一次发起多次生成以减少等待。",
+  "maximum": 4,
+  "minimum": 1,
+  "title": "Request Count",
+  "type": "integer"
+}
    • changedInput schema / $defs / MultiImageFusionInput / properties / size / description
      Previous value: -"生成图片尺寸，可选 1K/2K/4K；未提供时使用全局默认值。"New value: +"生成图片尺寸，可选 1K/2K/3K/4K 或 <宽>x<高> 像素值；未提供时使用全局默认值。"
    • addedInput schema / $defs / MultiImageFusionInput / properties / tools
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/GenerationTool"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "模型工具配置，仅 doubao-seedream-5.0 支持，目前仅支持 web_search。",
+  "title": "Tools"
+}
    • 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: +"图片生成响应格式枚举"
    • 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_multi_image_fusionOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description indicates the tool generates new images, consistent with annotations (readOnlyHint=false, destructiveHint=false). However, it does not elaborate on side effects, memory usage, or behavior under specific conditions like failed inputs.

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?

The description is a single, efficient sentence with an example, conveying essential information without waste. It could be slightly more structured but is well-suited for quick comprehension.

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?

The description explains the core functionality but omits output details (e.g., format) and prerequisites. The rich schema compensates partially, but without an output schema, more contextual guidance would be beneficial.

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?

The tool description adds no parameter-specific details beyond the schema, but the nested schema provides comprehensive descriptions for each field. The description's lack of parameter info is acceptable as the schema already covers semantics.

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 'multi-image fusion' and provides specific examples like merging clothing with models or people with landscapes, making the tool's purpose unmistakable and distinguishing it from siblings like text-to-image or image-to-image.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives examples of when to use (e.g., outfit creation, portrait with scenery) but does not explicitly state when not to use or offer direct comparisons to sibling tools, leaving the agent to infer usage scenarios.

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