Seedance 2.0 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_stylesA | Return the canonical list of image-generation styles or presets the site exposes. (Seedance 2.0) |
| get_pricingB | Return the canonical pricing entry point for Seedance 2.0. |
| get_official_linksA | Return the canonical list of official links for Seedance 2.0 (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_seedance2video | Summarize what the site is, who it's for, and how it works. — Seedance 2.0 |
| try_image_style_seedance2video | Recommend a starting image-generation style for a stated goal. — Seedance 2.0 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| styles | Supported image-generation styles and presets. |
| pricing | Canonical pricing entry point. |
| docs | Canonical documentation entry point. |
| faq | Short FAQ generated from public site metadata. |
| links | Canonical URLs to share with users. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing styles, getting pricing, and retrieving official links. No ambiguity.
All tools follow a verb_noun pattern, but the verbs differ: 'list' vs 'get'. This minor inconsistency is clear but not perfectly uniform.
With 3 tools, the server is on the small side but could be appropriate for a simple info-only service. However, given the domain (image generation), more tools would be expected.
The tool set is severely incomplete for an image generation service. Missing core tools like generate_image or fetch_generation, leaving obvious gaps.