Skip to main content
Glama
Sign In
Seedream/Seedance MCP Server

Seedream/Seedance MCP Server

by nsmao-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

text-to-image

Generate images from text prompts using Volcengine's Seedream models, specifying dimensions, styles, and optional reference images for creative visual content.

Instructions

使用火山方舟 Seedream 模型生成图片（Ark-only）

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>",
      "ratio": "<ratio>"
    },
    "name": "text-to-image"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYes图片生成提示词
ratioYes生成图像宽高
styleNo可选风格描述，会自动拼接到提示词中
modelNo模型ID，默认5.0-lite
model_versionNo兼容旧参数：v4.0会映射到doubao-seedream-4-0-250828
image_urlsNo参考图URL数组
add_watermarkNo是否添加水印

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the model provider and exclusivity ('Ark-only'), it doesn't describe important behavioral aspects such as rate limits, authentication requirements, response format, error conditions, or whether the operation is idempotent. For a generative AI tool with no annotation coverage, this represents a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single Chinese sentence that efficiently communicates the core functionality and platform specificity. There's no wasted language or redundancy. The structure is front-loaded with the essential information: tool purpose and model provider.

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 complex image generation tool with 7 parameters, no annotations, and no output schema, the description is insufficiently complete. While concise, it doesn't address critical contextual information such as output format (image URL? binary data?), error handling, rate limits, or how it differs from similar sibling tools. The absence of annotations and output schema means the description should provide more comprehensive guidance.

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 description provides no parameter-specific information beyond what's already documented in the input schema, which has 100% coverage. All 7 parameters (prompt, ratio, style, model, model_version, image_urls, add_watermark) are well-described in the schema with clear descriptions and enums where applicable. The description adds no additional context about parameter usage, constraints, or interactions.

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?

The description clearly states the tool's purpose: '生成图片' (generate images) using the '火山方舟 Seedream 模型' (Volcano Ark Seedream model). It specifies the model provider and includes '(Ark-only)' to indicate exclusivity. However, it doesn't explicitly differentiate from sibling tools like 'generate-image' or 'generate-img-seedream4', which appear to offer similar functionality.

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?

The description provides minimal usage guidance. It mentions '(Ark-only)' which suggests this tool is specific to the Volcano Ark platform, but offers no explicit guidance on when to use this tool versus the sibling tools like 'generate-image' or 'generate-img-seedream4'. There's no mention of prerequisites, alternatives, or specific scenarios where this tool is preferred.

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