SeedanceMCP
SeedanceMCP
ByteDance Seedance を AceDataCloud API 経由で利用するための Model Context Protocol (MCP) サーバーです。
Claude、VS Code、またはMCP互換クライアントから直接AI動画を生成できます。
機能
テキストから動画生成 - テキストプロンプトからAI動画を作成
画像から動画生成 - 開始フレーム、終了フレーム、参照画像制御による画像のアニメーション化
複数のモデル - Seedance 1.5 Pro、1.0 Pro、1.0 Pro Fast、1.0 Lite T2V/I2Vをサポート
複数の解像度 - 480p、720p(デフォルト)、1080pの出力に対応
柔軟なアスペクト比 - 16:9、9:16、1:1、4:3、3:4、21:9、およびアダプティブ
オーディオ生成 - 動画用の同期オーディオを生成(1.5 Pro)
サービスティア - デフォルト(優先)およびFlex(コスト効率重視)の処理
タスク追跡 - 生成の進捗状況を監視し、結果を取得
Related MCP server: seedance-2-mcp
ツールリファレンス
ツール | 説明 |
| ByteDance Seedanceを使用してテキストプロンプトからAI動画を生成します。 |
| ByteDance Seedanceを使用して参照画像からAI動画を生成します。 |
| 動画生成タスクのステータスと結果を照会します。 |
| 複数の動画生成タスクを一度に照会します。 |
| 利用可能なすべてのSeedanceモデルとその機能および価格を一覧表示します。 |
| Seedanceで利用可能なすべての解像度とアスペクト比を一覧表示します。 |
| 利用可能なすべてのSeedance APIアクションと対応するツールを一覧表示します。 |
クイックスタート
1. APIトークンの取得
AceDataCloud Platform にサインアップ
APIドキュメントページ に移動
「Acquire」 をクリックしてAPIトークンを取得
トークンをコピーして以下で使用
2. ホスト型サーバーの使用(推奨)
AceDataCloudが管理するMCPサーバーをホストしているため、ローカルインストールは不要です。
エンドポイント: https://seedance.mcp.acedata.cloud/mcp
すべてのリクエストにはBearerトークンが必要です。ステップ1で取得したAPIトークンを使用してください。
Claude.ai
Claude.ai でOAuthを使用して直接接続します(APIトークン不要):
Claude.aiの 設定 → 統合 → 追加 に移動
サーバーURLを入力:
https://seedance.mcp.acedata.cloud/mcpOAuthログインフローを完了
会話内でツールの使用を開始
Claude Desktop
設定ファイル(macOSの場合は ~/Library/Application Support/Claude/claude_desktop_config.json)に追加:
{
"mcpServers": {
"seedance": {
"type": "streamable-http",
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}Cursor / Windsurf
MCP設定(.cursor/mcp.json または .windsurf/mcp.json)に追加:
{
"mcpServers": {
"seedance": {
"type": "streamable-http",
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}VS Code (Copilot)
VS CodeのMCP設定(.vscode/mcp.json)に追加:
{
"servers": {
"seedance": {
"type": "streamable-http",
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}または、VS Code用の Ace Data Cloud MCP拡張機能 をインストールしてください。15個のMCPサーバーすべてをワンクリックでセットアップできます。
JetBrains IDEs
設定 → ツール → AI Assistant → Model Context Protocol (MCP) に移動
追加 → HTTP をクリック
以下を貼り付け:
{
"mcpServers": {
"seedance": {
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}Claude Code
Claude CodeはMCPサーバーをネイティブでサポートしています:
claude mcp add seedance --transport http https://seedance.mcp.acedata.cloud/mcp \
-h "Authorization: Bearer YOUR_API_TOKEN"または、プロジェクトの .mcp.json に追加:
{
"mcpServers": {
"seedance": {
"type": "streamable-http",
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}Cline
ClineのMCP設定(.cline/mcp_settings.json)に追加:
{
"mcpServers": {
"seedance": {
"type": "streamable-http",
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}Amazon Q Developer
MCP設定に追加:
{
"mcpServers": {
"seedance": {
"type": "streamable-http",
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}Roo Code
Roo CodeのMCP設定に追加:
{
"mcpServers": {
"seedance": {
"type": "streamable-http",
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}Continue.dev
.continue/config.yaml に追加:
mcpServers:
- name: seedance
type: streamable-http
url: https://seedance.mcp.acedata.cloud/mcp
headers:
Authorization: "Bearer YOUR_API_TOKEN"Zed
Zedの設定(~/.config/zed/settings.json)に追加:
{
"language_models": {
"mcp_servers": {
"seedance": {
"url": "https://seedance.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
}cURLテスト
# Health check (no auth required)
curl https://seedance.mcp.acedata.cloud/health
# MCP initialize
curl -X POST https://seedance.mcp.acedata.cloud/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'3. ローカルでの実行(代替手段)
サーバーを自分のマシンで実行したい場合:
# Install from PyPI
pip install mcp-seedance
# or
uvx mcp-seedance
# Set your API token
export ACEDATACLOUD_API_TOKEN="your_token_here"
# Run (stdio mode for Claude Desktop / local clients)
mcp-seedance
# Run (HTTP mode for remote access)
mcp-seedance --transport http --port 8000Claude Desktop (ローカル)
{
"mcpServers": {
"seedance": {
"command": "uvx",
"args": ["mcp-seedance"],
"env": {
"ACEDATACLOUD_API_TOKEN": "your_token_here"
}
}
}
}Docker (セルフホスト)
docker pull ghcr.io/acedatacloud/mcp-seedance:latest
docker run -p 8000:8000 ghcr.io/acedatacloud/mcp-seedance:latestクライアントは独自のBearerトークンで接続します。サーバーは各リクエストの Authorization ヘッダーからトークンを抽出します。
利用可能なツール
動画生成
ツール | 説明 |
| テキストプロンプトから動画を生成 |
| 参照/開始/終了画像を使用して動画を生成 |
タスク
ツール | 説明 |
| 単一のタスクステータスを照会 |
| 複数のタスクを一度に照会 |
情報
ツール | 説明 |
| 利用可能なSeedanceモデルを一覧表示 |
| 利用可能な出力解像度を一覧表示 |
| 利用可能なAPIアクションを一覧表示 |
使用例
プロンプトから動画を生成
User: Create a video of a cat playing with a ball of yarn
Claude: I'll generate a video for you.
[Calls seedance_generate_video with prompt="A cute cat playfully batting a ball of yarn"]画像をアニメーション化
User: Turn this image into a video: https://example.com/landscape.jpg
Claude: I'll create a video from your image.
[Calls seedance_generate_video_from_image with first_frame_url and appropriate prompt]オーディオ付きで生成
User: Create a video of rain falling with sound
Claude: I'll generate a video with synchronized audio.
[Calls seedance_generate_video with prompt="Rain falling on a quiet street" and generate_audio=True, model="doubao-seedance-1-5-pro-251215"]利用可能なモデル
モデル | 説明 | 機能 |
| 2.0 | 最新の生成品質 |
| 2.0 Fast | 最新の高速生成 |
| 1.5 Pro | オーディオ生成、T2V、I2V |
| 1.0 Pro (デフォルト) | 高品質T2V、I2V |
| 1.0 Pro Fast | 高速生成 |
| 1.0 Lite T2V | 軽量テキストから動画生成 |
| 1.0 Lite I2V | 軽量画像から動画生成 |
利用可能なアスペクト比
アスペクト比 | 説明 | 用途 |
| 横長 (デフォルト) | YouTube、TV、プレゼンテーション |
| 縦長 | TikTok、Instagram Reels |
| 正方形 | Instagram投稿 |
| 伝統的 | クラシックな動画形式 |
| 伝統的な縦長 | 縦長コンテンツ |
| ウルトラワイド | シネマティックコンテンツ |
| アダプティブ | 画像から自動検出 |
設定
環境変数
変数 | 説明 | デフォルト |
| AceDataCloudのAPIトークン | 必須 |
| APIベースURL |
|
| OAuthクライアントID (ホストモード) | — |
| プラットフォームベースURL |
|
| デフォルトモデル |
|
| デフォルト解像度 |
|
| デフォルトアスペクト比 |
|
| デフォルト時間 (秒) |
|
| リクエストタイムアウト (秒) |
|
| ログレベル |
|
コマンドラインオプション
mcp-seedance --help
Options:
--version Show version
--transport Transport mode: stdio (default) or http
--port Port for HTTP transport (default: 8000)開発
開発環境のセットアップ
# Clone repository
git clone https://github.com/AceDataCloud/SeedanceMCP.git
cd SeedanceMCP
# Create virtual environment
python -m venv .venv
source .venv/bin/activate # or `.venv\Scripts\activate` on Windows
# Install with dev dependencies
pip install -e ".[dev,test]"テストの実行
# Run unit tests
pytest
# Run with coverage
pytest --cov=core --cov=tools
# Run integration tests (requires API token)
pytest tests/test_integration.py -m integrationコード品質
# Format code
ruff format .
# Lint code
ruff check .
# Type check
mypy core toolsビルドと公開
# Install build dependencies
pip install -e ".[release]"
# Build package
python -m build
# Upload to PyPI
twine upload dist/*プロジェクト構造
SeedanceMCP/
├── core/ # Core modules
│ ├── __init__.py
│ ├── client.py # HTTP client for Seedance API
│ ├── config.py # Configuration management
│ ├── exceptions.py # Custom exceptions
│ ├── server.py # MCP server initialization
│ ├── types.py # Type definitions
│ └── utils.py # Utility functions
├── tools/ # MCP tool definitions
│ ├── __init__.py
│ ├── video_tools.py # Video generation tools
│ ├── task_tools.py # Task query tools
│ └── info_tools.py # Information tools
├── prompts/ # MCP prompts
│ └── __init__.py # Prompt templates
├── tests/ # Test suite
│ ├── conftest.py
│ ├── test_client.py
│ ├── test_config.py
│ ├── test_integration.py
│ └── test_utils.py
├── deploy/ # Deployment configs
│ └── production/
│ ├── deployment.yaml
│ ├── ingress.yaml
│ └── service.yaml
├── .env.example # Environment template
├── .gitignore
├── CHANGELOG.md
├── Dockerfile # Docker image for HTTP mode
├── docker-compose.yaml # Docker Compose config
├── LICENSE
├── main.py # Entry point
├── pyproject.toml # Project configuration
└── README.mdAPIリファレンス
このサーバーは AceDataCloud Seedance API をラップしています:
Seedance Videos API - 動画生成
Seedance Tasks API - タスク照会
コントリビューション
コントリビューションを歓迎します!以下の手順に従ってください:
リポジトリをフォーク
フィーチャーブランチを作成 (
git checkout -b feature/amazing)変更をコミット (
git commit -m 'Add amazing feature')ブランチにプッシュ (
git push origin feature/amazing)プルリクエストを開く
ライセンス
MITライセンス - 詳細は LICENSE を参照してください。
リンク
Made with love by AceDataCloud
Available Tools
7 toolsseedance_generate_videoAInspect
Generate AI video from a text prompt using ByteDance Seedance.
This is the simplest way to create video - just describe what you want and
Seedance will generate a high-quality AI video.
Use this when:
- You want to create a video from a text description
- You don't have reference images
- You want quick text-to-video generation
For using reference images (first/last frame, reference), use
seedance_generate_video_from_image instead.
Returns:
Task ID and generated video information including URLs and metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | Random seed for reproducible generation. Range: -1 to 4294967295. Use -1 for random. Default is -1. | |
| model | No | Model version to use. Options: 'doubao-seedance-2-5-260628' (latest flagship, up to 30 seconds, multimodal reference, edit/extend, default), 'doubao-seedance-2-0-260128' (highest resolution, supports 4k), 'doubao-seedance-2-0-fast-260128' (latest generation, faster, up to 720p), 'doubao-seedance-2-0-mini-260615' (latest generation, lightweight, cheapest within the 2.0 series, up to 720p), 'doubao-seedance-1-5-pro-251215' (1.5 flagship, supports audio), 'doubao-seedance-1-0-pro-250528' (1.0 standard), 'doubao-seedance-1-0-pro-fast-251015' (1.0 fast, cost-optimized), 'doubao-seedance-1-0-lite-t2v-250428' (lightweight text-to-video), 'doubao-seedance-1-0-lite-i2v-250428' (lightweight image-to-video). | doubao-seedance-2-0-260128 |
| ratio | No | Video aspect ratio. Options: '16:9' (landscape, default), '9:16' (portrait), '1:1' (square), '4:3', '3:4', '21:9' (ultrawide), 'adaptive'. | 16:9 |
| tools | No | Optional Seedance 2.5 web search tool configuration. | |
| frames | No | Frame count for the generated video (1.0 series only). Must satisfy 25+4n (e.g. 29, 33, 37, ..., 289). Mutually exclusive with 'duration'. | |
| prompt | Yes | Description of the video to generate. Max 1000 characters. Be descriptive about the scene, motion, style, and mood. You can also include inline parameters like '--rs 720p --rt 16:9 --dur 5'. Examples: 'A cat walking through a garden with butterflies', 'Cinematic aerial shot of mountains at sunset' | |
| duration | No | Video duration in seconds. 1.0 series: 2–12; 1.5 Pro: 4–12; 2.0 series: 4–15; 2.5: 4–30. Use -1 for auto-duration (1.5 Pro and 2.x). Default is 5. Mutually exclusive with 'frames'. | |
| priority | No | Seedance 2.5 task priority from 0 to 9. | |
| watermark | No | If true, add a watermark to the video. Default is false. | |
| resolution | No | Video resolution. Options: '480p', '720p' (default), '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-5' maxes out at '1080p'; '2-0-fast' and '2-0-mini' max out at '720p'. | 720p |
| callback_url | No | Webhook callback URL for asynchronous notifications. When provided, the API returns immediately with a task_id and calls this URL when the video is generated. | |
| camera_fixed | No | If true, keep the camera fixed during generation. Default is false. | |
| output_format | No | Seedance 2.5 output format: mp4 or mov. | |
| generate_audio | No | If true, generate audio along with the video. Supported by 'doubao-seedance-1-5-pro-251215' and the 'doubao-seedance-2-0' series; other models ignore it. Approximately doubles the cost. Default is false. | |
| return_last_frame | No | If true, also return the last frame of the generated video as an image URL. Useful for video extension workflows. Default is false. | |
| safety_identifier | No | Stable anonymous end-user identifier. Do not use personal information. | |
| execution_expires_after | No | Task timeout threshold in seconds. Default is 172800 (48 hours). |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It does add a Returns clause mentioning task ID, video URLs, and metadata, which hints at task-based behavior. However, it omits important operational traits such as generation taking significant time and the likely need to poll or wait for the final video.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: action, use cases, alternative, and return summary come in a readable order. The 'simplest way / high-quality' sentence is slightly promotional and redundant with the first sentence, but it does not meaningfully inflate the length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 17-parameter tool, the input schema covers most details and an output schema presumably documents return structure. The description covers primary use cases and sibling routing, but it does not explain how to retrieve the final result, e.g., via seedance_get_task, or warn about long-running generation. It is adequate but has clear gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already documents all 17 parameters with defaults, enums, and model-specific constraints. The description adds little beyond identifying the prompt as the core input and clarifying this is the text-only variant, so the parameter burden is adequately carried by the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Generate AI video from a text prompt using ByteDance Seedance.' It also names the sibling seedance_generate_video_from_image, so an agent can immediately distinguish text-to-video generation from image-conditioned generation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'Use this when' bullets clearly define the conditions: creating video from text, no reference images, and quick text-to-video generation. It explicitly directs image-reference workflows to seedance_generate_video_from_image instead, which is excellent routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
seedance_generate_video_from_imageAInspect
Generate AI video using reference images with ByteDance Seedance.
This allows you to control the video by specifying first frame, last frame,
or reference images. Seedance will generate smooth motion based on the inputs.
Use this when:
- You have a specific image you want to animate
- You want to create a video transition between two images
- You need style guidance from reference images
- You need precise control over the video's visual content
Note: reference_image_urls cannot be combined with first_frame_url/last_frame_url.
At least one image input must be provided.
Returns:
Task ID and generated video information including URLs and metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | Random seed. -1 for random. Default is -1. | |
| model | No | Model version to use. Use 'doubao-seedance-2-0-260128' (default) for latest-generation quality and multimodal reference, 'doubao-seedance-2-0-fast-260128' or 'doubao-seedance-2-0-mini-260615' for faster/cheaper 2.0, or a 1.x model such as 'doubao-seedance-1-0-lite-i2v-250428' for lightweight I2V. | doubao-seedance-2-0-260128 |
| ratio | No | Video aspect ratio. Use 'adaptive' to match your input image ratio. | 16:9 |
| tools | No | Optional Seedance 2.5 web search tool configuration. | |
| frames | No | Frame count for the generated video (1.0 series only). Must satisfy 25+4n (e.g. 29, 33, 37, ..., 289). Mutually exclusive with 'duration'. | |
| prompt | Yes | Description of the video motion and content. Describe what should happen in the video, how objects should move, what transitions to include. | |
| duration | No | Video duration in seconds. 1.0 series: 2–12; 1.5 Pro: 4–12; 2.0 series: 4–15; 2.5: 4–30. Use -1 for auto-duration (1.5 Pro and 2.x). Default is 5. Mutually exclusive with 'frames'. | |
| priority | No | Seedance 2.5 task priority from 0 to 9. | |
| resolution | No | Video resolution. Options: '480p', '720p', '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-5' maxes out at '1080p'; '2-0-fast' and '2-0-mini' max out at '720p'. | 720p |
| callback_url | No | Webhook callback URL for asynchronous notifications. | |
| output_format | No | Seedance 2.5 output format: mp4 or mov. | |
| generate_audio | No | If true, generate audio. Supported by 'doubao-seedance-1-5-pro-251215' and the Seedance 2.x series. Default is false. | |
| last_frame_url | No | URL of the image to use as the last frame of the video. The video will animate towards this image. Supports https:// URLs or base64 data:image/... URIs. | |
| first_frame_url | No | URL of the image to use as the first frame of the video. The video will animate from this image. Supports https:// URLs or base64 data:image/... URIs. | |
| return_last_frame | No | If true, return the last frame of the generated video. Default is false. | |
| safety_identifier | No | Stable anonymous end-user identifier. Do not use personal information. | |
| reference_audio_urls | No | Seedance 2.0 only. Reference audio URLs (up to 3) for voice timbre / background music. Ignored by 1.x models. | |
| reference_image_urls | No | List of reference image URLs for style/content guidance. For the Seedance 2.0 series these can be real-person / character references that keep the subject consistent (up to 9). These images influence the look but are not used as frames. Cannot be combined with first_frame_url or last_frame_url. | |
| reference_video_urls | No | Seedance 2.0 only. Reference video URLs (up to 3) for subject, camera movement, motion or overall style. Ignored by 1.x models. | |
| execution_expires_after | No | Task timeout threshold in seconds. Default is 172800 (48 hours). | |
| omni_reference_task_type | No | Seedance 2.5 task type: auto, reference, edit, or extend. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It discloses the mutual exclusivity constraint between reference images and frame URLs, and notes that at least one image must be provided. It also states the return value (task ID and video info). Though it doesn't detail async behavior or polling requirements, this is reasonable coverage for a generation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-organized with a lead sentence, usage bullets, a constraint note, and a returns section. It is slightly longer than strictly necessary but every section adds value, and the most critical constraint is called out explicitly near the end of the main text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 21 parameters and no annotations, the description does a good job capturing the essential behavioral context: image input modes, mutual exclusivity, and required input. The return-value section is present, and the schema covers parameter details. Minor omissions like asynchronous/polling behavior are not fatal because the output schema provides return structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already explains every parameter. The description adds meaning by grouping input modes (first frame, last frame, reference images) and highlighting the interaction constraint among them. It doesn't restate each parameter but adds selection-level semantics that the flat schema lacks.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that this tool generates AI video from reference images using ByteDance Seedance, distinguishing it from the sibling seedance_generate_video (which presumably lacks image control). It explicitly names the input modes (first frame, last frame, reference images) and supports this with concrete usage cases.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when-to-use bullet points and a critical exclusion rule: reference_image_urls cannot be combined with first_frame_url/last_frame_url. It also mandates at least one image input. This is strong guidance for tool selection and correct invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
seedance_get_taskAInspect
Query the status and result of a video generation task.
Use this to check if a generation is complete and retrieve the resulting
video URLs, thumbnails, and other metadata.
Use this when:
- You want to check if a generation has completed
- You need to retrieve video URLs from a previous generation
- You want to get the full details of a generated video
Task statuses:
- 'running': Generation is still in progress
- 'succeeded': Generation finished successfully
- 'failed': Generation failed (check error message)
Returns:
Task status and generated video information including URLs and metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | The task ID returned from a generation request. This is the 'task_id' field from any seedance_generate_* tool response. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, but description covers task statuses and error handling. Read-only nature implied, but no mention of auth or rate limits; adequate for simplicity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Efficient use of bullet points for statuses and returns. Front-loaded key purpose, no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given output schema exists and tool is simple, description covers all necessary context: statuses, return content, and usage rationale.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage 100% with parameter description. Description adds value by specifying source of task_id (from generation response).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb 'Query' and resource 'status and result of a video generation task'. Clearly distinguishes from sibling generation and list tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit usage scenarios (check completion, retrieve URLs, get details). No explicit when-not, but context is clear for a query tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
seedance_get_tasks_batchAInspect
Query multiple video generation tasks at once.
Efficiently check the status of multiple tasks in a single request.
More efficient than calling seedance_get_task multiple times.
Use this when:
- You have multiple pending generations to check
- You want to get status of several videos at once
- You're tracking a batch of generations
Returns:
Status and video information for all queried tasks.
| Name | Required | Description | Default |
|---|---|---|---|
| task_ids | Yes | List of task IDs to query. Maximum recommended batch size is 50 tasks. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but description implies a safe read operation by calling it a query. Mentions batch limit in schema, which adds practical info. Could explicitly state read-only nature.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Concise, front-loaded with purpose, then usage guidelines, then returns. Every sentence adds value with no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has a simple interface (1 param, output schema exists). Description covers all necessary aspects: purpose, usage context, and return summary. Minor gap: no explicit safety statement.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers parameter semantics fully (100% coverage) with description of task_ids and batch limit. Main description adds only context about batching and returns, but no extra parameter meaning beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Query multiple video generation tasks at once' and distinguishes itself from sibling tool `seedance_get_task` by emphasizing batching efficiency.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly lists when to use the tool with bullet points and compares to the sibling tool, stating 'More efficient than calling seedance_get_task multiple times'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
seedance_list_actionsAInspect
List all available Seedance API actions and corresponding tools.
Reference guide for what each action does and which tool to use.
Helpful for understanding the full capabilities of the Seedance MCP.
Returns:
Categorized list of all actions and their corresponding tools.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Clearly describes the operation as a listing of actions/tools returning a categorized list, which is transparent for a read-only operation; no annotations provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Concise three-sentence description front-loads the purpose and return value, with no unnecessary information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and presence of an output schema, the description adequately covers purpose, output, and utility without gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters, but description adds meaningful context about the return value (categorized list of actions and tools) beyond the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it lists all Seedance API actions and corresponding tools, distinguishing it from sibling tools that generate videos, get tasks, or list models.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied use as a reference guide for understanding capabilities, but no explicit when-to-use or when-not-to-use guidance compared to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
seedance_list_modelsAInspect
List all available Seedance models with their capabilities and pricing.
Shows all available model options with their features, strengths, and costs.
Use this to understand which model to choose for your video generation.
Returns:
Table of all models with descriptions, capabilities, and pricing.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool lists models with capabilities and pricing, implying a read-only operation with no side effects. This is adequate for a simple list tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, each contributing to the purpose, usage, and return value. It is concise without being overly terse, though some minor redundancy exists ('Shows all available model options' repeats the first sentence).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and the existence of an output schema, the description adequately covers the tool's purpose, usage, and return value. No further information is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and schema coverage is 100%. The baseline for 0 parameters is 4. The description does not need to add parameter information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'List all available Seedance models with their capabilities and pricing.' This is a specific verb+resource combination that distinguishes it from sibling tools like seedance_generate_video or seedance_get_task.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes 'Use this to understand which model to choose for your video generation,' providing clear context for when to use the tool. It does not explicitly state when not to use alternatives, but the purpose is simple enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
seedance_list_resolutionsAInspect
List all available resolutions and aspect ratios for Seedance.
Shows all available resolution and aspect ratio options with use cases.
Returns:
Tables of resolutions and aspect ratios with descriptions.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description transparently states it returns tables of resolutions and aspect ratios with descriptions. It adds value beyond a simple 'list' by mentioning use cases and descriptions, though it does not detail freshness or caching behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with two sentences and a 'Returns:' clause. Every sentence adds value, and the structure is front-loaded with the primary action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and an output schema, the description fully covers what the tool does and returns. It is complete for a simple listing tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, and schema description coverage is 100%. Per baseline, score 4 is appropriate as the description does not need to add parameter info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool lists all available resolutions and aspect ratios for Seedance. It clearly distinguishes itself from sibling tools like seedance_list_models or seedance_list_actions by focusing on resolution options.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context (before generating a video) but provides no explicit when/when-not guidance or alternatives. The agent can infer use, but lacks explicit direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.1.11- Changed
seedance_generate_video_from_image2 fields changed- changed
Input schema / properties / omni_reference_task_type / anyOfPrevious value: -[ - { - "enum": [ - "auto", - "edit", - "extend" - ], - "type": "string" - }, - { - "type": "null" - } -]New value: +[ + { + "enum": [ + "auto", + "reference", + "edit", + "extend" + ], + "type": "string" + }, + { + "type": "null" + } +] - changed
Input schema / properties / omni_reference_task_type / descriptionPrevious value: -"Seedance 2.5 task type: auto, edit, or extend."New value: +"Seedance 2.5 task type: auto, reference, edit, or extend."
2 tool updates
v0.1.10- Changed
seedance_generate_video2 fields changed- added
Input schema / properties / execution_expires_after / maximumAdded value: +259200 - added
Input schema / properties / execution_expires_after / minimumAdded value: +3600
- Changed
seedance_generate_video_from_image2 fields changed- added
Input schema / properties / execution_expires_after / maximumAdded value: +259200 - added
Input schema / properties / execution_expires_after / minimumAdded value: +3600
2 tool updates
v0.1.9- Changed
seedance_generate_video6 fields changed- added
Input schema / $defsAdded value: +{ + "SeedanceWebSearchTool": { + "additionalProperties": false, + "description": "Seedance web search tool configuration.", + "properties": { + "limit": { + "default": 10, + "maximum": 50, + "minimum": 1, + "title": "Limit", + "type": "integer" + }, + "max_keyword": { + "anyOf": [ + { + "maximum": 50, + "minimum": 1, + "type": "integer" + }, + { + "type": "null" + } + ], + "default": null, + "title": "Max Keyword" + }, + "sources": { + "anyOf": [ + { + "items": { + "enum": [ + "toutiao", + "douyin", + "moji", + "search_engine" + ], + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "title": "Sources" + }, + "type": { + "const": "web_search", + "title": "Type", + "type": "string" + } + }, + "required": [ + "type" + ], + "title": "SeedanceWebSearchTool", + "type": "object" + } +} - added
Input schema / properties / priorityAdded value: +{ + "default": 0, + "description": "Seedance 2.5 task priority from 0 to 9.", + "maximum": 9, + "minimum": 0, + "title": "Priority", + "type": "integer" +} - changed
Input schema / properties / resolution / descriptionPrevious value: -"Video resolution. Options: '480p', '720p' (default), '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-0-fast' and '2-0-mini' max out at '720p'."New value: +"Video resolution. Options: '480p', '720p' (default), '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-5' maxes out at '1080p'; '2-0-fast' and '2-0-mini' max out at '720p'." - added
Input schema / properties / safety_identifierAdded value: +{ + "anyOf": [ + { + "maxLength": 64, + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Stable anonymous end-user identifier. Do not use personal information.", + "title": "Safety Identifier" +} - changed
Input schema / properties / tools / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": true, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "$ref": "#/$defs/SeedanceWebSearchTool" + }, + "maxItems": 1, + "type": "array" + }, + { + "type": "null" + } +] - changed
Input schema / properties / tools / descriptionPrevious value: -"Optional Seedance 2.5 tool configuration objects."New value: +"Optional Seedance 2.5 web search tool configuration."
- Changed
seedance_generate_video_from_image6 fields changed- added
Input schema / $defsAdded value: +{ + "SeedanceWebSearchTool": { + "additionalProperties": false, + "description": "Seedance web search tool configuration.", + "properties": { + "limit": { + "default": 10, + "maximum": 50, + "minimum": 1, + "title": "Limit", + "type": "integer" + }, + "max_keyword": { + "anyOf": [ + { + "maximum": 50, + "minimum": 1, + "type": "integer" + }, + { + "type": "null" + } + ], + "default": null, + "title": "Max Keyword" + }, + "sources": { + "anyOf": [ + { + "items": { + "enum": [ + "toutiao", + "douyin", + "moji", + "search_engine" + ], + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "title": "Sources" + }, + "type": { + "const": "web_search", + "title": "Type", + "type": "string" + } + }, + "required": [ + "type" + ], + "title": "SeedanceWebSearchTool", + "type": "object" + } +} - added
Input schema / properties / priorityAdded value: +{ + "default": 0, + "description": "Seedance 2.5 task priority from 0 to 9.", + "maximum": 9, + "minimum": 0, + "title": "Priority", + "type": "integer" +} - changed
Input schema / properties / resolution / descriptionPrevious value: -"Video resolution. Options: '480p', '720p', '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-0-fast' and '2-0-mini' max out at '720p'."New value: +"Video resolution. Options: '480p', '720p', '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-5' maxes out at '1080p'; '2-0-fast' and '2-0-mini' max out at '720p'." - added
Input schema / properties / safety_identifierAdded value: +{ + "anyOf": [ + { + "maxLength": 64, + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Stable anonymous end-user identifier. Do not use personal information.", + "title": "Safety Identifier" +} - changed
Input schema / properties / tools / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": true, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "$ref": "#/$defs/SeedanceWebSearchTool" + }, + "maxItems": 1, + "type": "array" + }, + { + "type": "null" + } +] - changed
Input schema / properties / tools / descriptionPrevious value: -"Optional Seedance 2.5 tool configuration objects."New value: +"Optional Seedance 2.5 web search tool configuration."
2 tool updates
v0.1.8- Changed
seedance_generate_video9 fields changed- changed
Input schema / properties / duration / anyOfPrevious value: -[ - { - "maximum": 15, - "minimum": 2, - "type": "integer" - }, - { - "type": "null" - } -]New value: +[ + { + "maximum": 30, + "minimum": -1, + "type": "integer" + }, + { + "type": "null" + } +] - changed
Input schema / properties / duration / descriptionPrevious value: -"Video duration in seconds. Range: 2-15 (Seedance 2.0 supports 4-15). Default is 5. Mutually exclusive with 'frames'."New value: +"Video duration in seconds. 1.0 series: 2–12; 1.5 Pro: 4–12; 2.0 series: 4–15; 2.5: 4–30. Use -1 for auto-duration (1.5 Pro and 2.x). Default is 5. Mutually exclusive with 'frames'." - changed
Input schema / properties / frames / anyOfPrevious value: -[ - { - "type": "integer" - }, - { - "type": "null" - } -]New value: +[ + { + "maximum": 289, + "minimum": 29, + "type": "integer" + }, + { + "type": "null" + } +] - changed
Input schema / properties / frames / descriptionPrevious value: -"Frame count for the generated video. Must satisfy 25+4n (e.g. 29, 33, 37, ..., 361). Mutually exclusive with 'duration'."New value: +"Frame count for the generated video (1.0 series only). Must satisfy 25+4n (e.g. 29, 33, 37, ..., 289). Mutually exclusive with 'duration'." - changed
Input schema / properties / model / descriptionPrevious value: -"Model version to use. Options: 'doubao-seedance-2-0-260128' (latest generation, highest quality, supports 4k and multimodal reference, default), 'doubao-seedance-2-0-fast-260128' (latest generation, faster, up to 720p), 'doubao-seedance-2-0-mini-260615' (latest generation, lightweight, cheapest within the 2.0 series, up to 720p), 'doubao-seedance-1-5-pro-251215' (1.5 flagship, supports audio), 'doubao-seedance-1-0-pro-250528' (1.0 standard), 'doubao-seedance-1-0-pro-fast-251015' (1.0 fast, cost-optimized), 'doubao-seedance-1-0-lite-t2v-250428' (lightweight text-to-video), 'doubao-seedance-1-0-lite-i2v-250428' (lightweight image-to-video)."New value: +"Model version to use. Options: 'doubao-seedance-2-5-260628' (latest flagship, up to 30 seconds, multimodal reference, edit/extend, default), 'doubao-seedance-2-0-260128' (highest resolution, supports 4k), 'doubao-seedance-2-0-fast-260128' (latest generation, faster, up to 720p), 'doubao-seedance-2-0-mini-260615' (latest generation, lightweight, cheapest within the 2.0 series, up to 720p), 'doubao-seedance-1-5-pro-251215' (1.5 flagship, supports audio), 'doubao-seedance-1-0-pro-250528' (1.0 standard), 'doubao-seedance-1-0-pro-fast-251015' (1.0 fast, cost-optimized), 'doubao-seedance-1-0-lite-t2v-250428' (lightweight text-to-video), 'doubao-seedance-1-0-lite-i2v-250428' (lightweight image-to-video)." - changed
Input schema / properties / model / enumPrevious value: -[ - "doubao-seedance-2-0-260128", - "doubao-seedance-2-0-fast-260128", - "doubao-seedance-2-0-mini-260615", - "doubao-seedance-1-5-pro-251215", - "doubao-seedance-1-0-pro-250528", - "doubao-seedance-1-0-pro-fast-251015", - "doubao-seedance-1-0-lite-t2v-250428", - "doubao-seedance-1-0-lite-i2v-250428" -]New value: +[ + "doubao-seedance-2-5-260628", + "doubao-seedance-2-0-260128", + "doubao-seedance-2-0-fast-260128", + "doubao-seedance-2-0-mini-260615", + "doubao-seedance-1-5-pro-251215", + "doubao-seedance-1-0-pro-250528", + "doubao-seedance-1-0-pro-fast-251015", + "doubao-seedance-1-0-lite-t2v-250428", + "doubao-seedance-1-0-lite-i2v-250428" +] - added
Input schema / properties / output_formatAdded value: +{ + "anyOf": [ + { + "enum": [ + "mp4", + "mov" + ], + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Seedance 2.5 output format: mp4 or mov.", + "title": "Output Format" +} - removed
Input schema / properties / service_tierRemoved value: -{ - "default": "default", - "description": "Service tier. 'default' for standard processing, 'flex' for 50%% cheaper but slower processing. Default is 'default'.", - "enum": [ - "default", - "flex" - ], - "title": "Service Tier", - "type": "string" -} - added
Input schema / properties / toolsAdded value: +{ + "anyOf": [ + { + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Optional Seedance 2.5 tool configuration objects.", + "title": "Tools" +}
- Changed
seedance_generate_video_from_image10 fields changed- changed
Input schema / properties / duration / anyOfPrevious value: -[ - { - "maximum": 15, - "minimum": 2, - "type": "integer" - }, - { - "type": "null" - } -]New value: +[ + { + "maximum": 30, + "minimum": -1, + "type": "integer" + }, + { + "type": "null" + } +] - changed
Input schema / properties / duration / descriptionPrevious value: -"Video duration in seconds. Range: 2-15 (Seedance 2.0 supports 4-15). Default is 5. Mutually exclusive with 'frames'."New value: +"Video duration in seconds. 1.0 series: 2–12; 1.5 Pro: 4–12; 2.0 series: 4–15; 2.5: 4–30. Use -1 for auto-duration (1.5 Pro and 2.x). Default is 5. Mutually exclusive with 'frames'." - changed
Input schema / properties / frames / anyOfPrevious value: -[ - { - "type": "integer" - }, - { - "type": "null" - } -]New value: +[ + { + "maximum": 289, + "minimum": 29, + "type": "integer" + }, + { + "type": "null" + } +] - changed
Input schema / properties / frames / descriptionPrevious value: -"Frame count for the generated video. Must satisfy 25+4n (e.g. 29, 33, 37, ..., 361). Mutually exclusive with 'duration'."New value: +"Frame count for the generated video (1.0 series only). Must satisfy 25+4n (e.g. 29, 33, 37, ..., 289). Mutually exclusive with 'duration'." - changed
Input schema / properties / generate_audio / descriptionPrevious value: -"If true, generate audio. Supported by 'doubao-seedance-1-5-pro-251215' and the 'doubao-seedance-2-0' series. Default is false."New value: +"If true, generate audio. Supported by 'doubao-seedance-1-5-pro-251215' and the Seedance 2.x series. Default is false." - changed
Input schema / properties / model / enumPrevious value: -[ - "doubao-seedance-2-0-260128", - "doubao-seedance-2-0-fast-260128", - "doubao-seedance-2-0-mini-260615", - "doubao-seedance-1-5-pro-251215", - "doubao-seedance-1-0-pro-250528", - "doubao-seedance-1-0-pro-fast-251015", - "doubao-seedance-1-0-lite-t2v-250428", - "doubao-seedance-1-0-lite-i2v-250428" -]New value: +[ + "doubao-seedance-2-5-260628", + "doubao-seedance-2-0-260128", + "doubao-seedance-2-0-fast-260128", + "doubao-seedance-2-0-mini-260615", + "doubao-seedance-1-5-pro-251215", + "doubao-seedance-1-0-pro-250528", + "doubao-seedance-1-0-pro-fast-251015", + "doubao-seedance-1-0-lite-t2v-250428", + "doubao-seedance-1-0-lite-i2v-250428" +] - added
Input schema / properties / omni_reference_task_typeAdded value: +{ + "anyOf": [ + { + "enum": [ + "auto", + "edit", + "extend" + ], + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Seedance 2.5 task type: auto, edit, or extend.", + "title": "Omni Reference Task Type" +} - added
Input schema / properties / output_formatAdded value: +{ + "anyOf": [ + { + "enum": [ + "mp4", + "mov" + ], + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Seedance 2.5 output format: mp4 or mov.", + "title": "Output Format" +} - removed
Input schema / properties / service_tierRemoved value: -{ - "default": "default", - "description": "Service tier. 'default' or 'flex' (50%% cheaper). Default is 'default'.", - "enum": [ - "default", - "flex" - ], - "title": "Service Tier", - "type": "string" -} - added
Input schema / properties / toolsAdded value: +{ + "anyOf": [ + { + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Optional Seedance 2.5 tool configuration objects.", + "title": "Tools" +}
2 tool updates
v0.1.7- Changed
seedance_generate_video9 fields changed- changed
Input schema / properties / duration / anyOfPrevious value: -[ - { - "maximum": 12, - "minimum": 2, - "type": "integer" - }, - { - "type": "null" - } -]New value: +[ + { + "maximum": 15, + "minimum": 2, + "type": "integer" + }, + { + "type": "null" + } +] - changed
Input schema / properties / duration / descriptionPrevious value: -"Video duration in seconds. Range: 2-12. Default is 5. Mutually exclusive with 'frames'."New value: +"Video duration in seconds. Range: 2-15 (Seedance 2.0 supports 4-15). Default is 5. Mutually exclusive with 'frames'." - changed
Input schema / properties / frames / descriptionPrevious value: -"Frame count for the generated video. Must satisfy 25+4n (e.g. 29, 33, 37, ..., 289). Mutually exclusive with 'duration'."New value: +"Frame count for the generated video. Must satisfy 25+4n (e.g. 29, 33, 37, ..., 361). Mutually exclusive with 'duration'." - changed
Input schema / properties / generate_audio / descriptionPrevious value: -"If true, generate audio along with the video. Only supported by 'doubao-seedance-1-5-pro-251215' model. Approximately doubles the cost. Default is false."New value: +"If true, generate audio along with the video. Supported by 'doubao-seedance-1-5-pro-251215' and the 'doubao-seedance-2-0' series; other models ignore it. Approximately doubles the cost. Default is false." - changed
Input schema / properties / model / defaultPrevious value: -"doubao-seedance-1-0-pro-250528"New value: +"doubao-seedance-2-0-260128" - changed
Input schema / properties / model / descriptionPrevious value: -"Model version to use. Options: 'doubao-seedance-2-0-260128' (latest generation quality model), 'doubao-seedance-2-0-fast-260128' (latest generation fast model), 'doubao-seedance-1-5-pro-251215' (newest flagship, supports audio), 'doubao-seedance-1-0-pro-250528' (standard, default), 'doubao-seedance-1-0-pro-fast-251015' (fast, cost-optimized), 'doubao-seedance-1-0-lite-t2v-250428' (lightweight text-to-video), 'doubao-seedance-1-0-lite-i2v-250428' (lightweight image-to-video)."New value: +"Model version to use. Options: 'doubao-seedance-2-0-260128' (latest generation, highest quality, supports 4k and multimodal reference, default), 'doubao-seedance-2-0-fast-260128' (latest generation, faster, up to 720p), 'doubao-seedance-2-0-mini-260615' (latest generation, lightweight, cheapest within the 2.0 series, up to 720p), 'doubao-seedance-1-5-pro-251215' (1.5 flagship, supports audio), 'doubao-seedance-1-0-pro-250528' (1.0 standard), 'doubao-seedance-1-0-pro-fast-251015' (1.0 fast, cost-optimized), 'doubao-seedance-1-0-lite-t2v-250428' (lightweight text-to-video), 'doubao-seedance-1-0-lite-i2v-250428' (lightweight image-to-video)." - changed
Input schema / properties / model / enumPrevious value: -[ - "doubao-seedance-1-5-pro-251215", - "doubao-seedance-1-0-pro-250528", - "doubao-seedance-1-0-pro-fast-251015", - "doubao-seedance-1-0-lite-t2v-250428", - "doubao-seedance-1-0-lite-i2v-250428", - "doubao-seedance-2-0-260128", - "doubao-seedance-2-0-fast-260128" -]New value: +[ + "doubao-seedance-2-0-260128", + "doubao-seedance-2-0-fast-260128", + "doubao-seedance-2-0-mini-260615", + "doubao-seedance-1-5-pro-251215", + "doubao-seedance-1-0-pro-250528", + "doubao-seedance-1-0-pro-fast-251015", + "doubao-seedance-1-0-lite-t2v-250428", + "doubao-seedance-1-0-lite-i2v-250428" +] - changed
Input schema / properties / resolution / descriptionPrevious value: -"Video resolution. Options: '480p', '720p' (default), '1080p'."New value: +"Video resolution. Options: '480p', '720p' (default), '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-0-fast' and '2-0-mini' max out at '720p'." - changed
Input schema / properties / resolution / enumPrevious value: -[ - "480p", - "720p", - "1080p" -]New value: +[ + "480p", + "720p", + "1080p", + "4k" +]
- Changed
seedance_generate_video_from_image12 fields changed- changed
Input schema / properties / duration / anyOfPrevious value: -[ - { - "maximum": 12, - "minimum": 2, - "type": "integer" - }, - { - "type": "null" - } -]New value: +[ + { + "maximum": 15, + "minimum": 2, + "type": "integer" + }, + { + "type": "null" + } +] - changed
Input schema / properties / duration / descriptionPrevious value: -"Video duration in seconds. Range: 2-12. Default is 5. Mutually exclusive with 'frames'."New value: +"Video duration in seconds. Range: 2-15 (Seedance 2.0 supports 4-15). Default is 5. Mutually exclusive with 'frames'." - changed
Input schema / properties / frames / descriptionPrevious value: -"Frame count for the generated video. Must satisfy 25+4n (e.g. 29, 33, 37, ..., 289). Mutually exclusive with 'duration'."New value: +"Frame count for the generated video. Must satisfy 25+4n (e.g. 29, 33, 37, ..., 361). Mutually exclusive with 'duration'." - changed
Input schema / properties / generate_audio / descriptionPrevious value: -"If true, generate audio. Only supported by 1.5 Pro model. Default is false."New value: +"If true, generate audio. Supported by 'doubao-seedance-1-5-pro-251215' and the 'doubao-seedance-2-0' series. Default is false." - changed
Input schema / properties / model / defaultPrevious value: -"doubao-seedance-1-0-pro-250528"New value: +"doubao-seedance-2-0-260128" - changed
Input schema / properties / model / descriptionPrevious value: -"Model version to use. Use 'doubao-seedance-2-0-260128' for latest generation quality, 'doubao-seedance-2-0-fast-260128' for latest generation speed, For image-to-video, consider 'doubao-seedance-1-0-lite-i2v-250428' for lightweight I2V, or any Pro model for higher quality."New value: +"Model version to use. Use 'doubao-seedance-2-0-260128' (default) for latest-generation quality and multimodal reference, 'doubao-seedance-2-0-fast-260128' or 'doubao-seedance-2-0-mini-260615' for faster/cheaper 2.0, or a 1.x model such as 'doubao-seedance-1-0-lite-i2v-250428' for lightweight I2V." - changed
Input schema / properties / model / enumPrevious value: -[ - "doubao-seedance-1-5-pro-251215", - "doubao-seedance-1-0-pro-250528", - "doubao-seedance-1-0-pro-fast-251015", - "doubao-seedance-1-0-lite-t2v-250428", - "doubao-seedance-1-0-lite-i2v-250428", - "doubao-seedance-2-0-260128", - "doubao-seedance-2-0-fast-260128" -]New value: +[ + "doubao-seedance-2-0-260128", + "doubao-seedance-2-0-fast-260128", + "doubao-seedance-2-0-mini-260615", + "doubao-seedance-1-5-pro-251215", + "doubao-seedance-1-0-pro-250528", + "doubao-seedance-1-0-pro-fast-251015", + "doubao-seedance-1-0-lite-t2v-250428", + "doubao-seedance-1-0-lite-i2v-250428" +] - added
Input schema / properties / reference_audio_urlsAdded value: +{ + "default": [], + "description": "Seedance 2.0 only. Reference audio URLs (up to 3) for voice timbre / background music. Ignored by 1.x models.", + "items": { + "type": "string" + }, + "title": "Reference Audio Urls", + "type": "array" +} - changed
Input schema / properties / reference_image_urls / descriptionPrevious value: -"List of reference image URLs for style/content guidance. These images influence the look but are not used as frames. Cannot be combined with first_frame_url or last_frame_url."New value: +"List of reference image URLs for style/content guidance. For the Seedance 2.0 series these can be real-person / character references that keep the subject consistent (up to 9). These images influence the look but are not used as frames. Cannot be combined with first_frame_url or last_frame_url." - added
Input schema / properties / reference_video_urlsAdded value: +{ + "default": [], + "description": "Seedance 2.0 only. Reference video URLs (up to 3) for subject, camera movement, motion or overall style. Ignored by 1.x models.", + "items": { + "type": "string" + }, + "title": "Reference Video Urls", + "type": "array" +} - changed
Input schema / properties / resolution / descriptionPrevious value: -"Video resolution. Options: '480p', '720p', '1080p'."New value: +"Video resolution. Options: '480p', '720p', '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-0-fast' and '2-0-mini' max out at '720p'." - changed
Input schema / properties / resolution / enumPrevious value: -[ - "480p", - "720p", - "1080p" -]New value: +[ + "480p", + "720p", + "1080p", + "4k" +]
7 tool updates
v0.1.5- Added
seedance_generate_video - Added
seedance_generate_video_from_image - Added
seedance_get_task - Added
seedance_get_tasks_batch - Added
seedance_list_actions - Added
seedance_list_models - Added
seedance_list_resolutions
7 tool updates
v0.1.3- Removed
seedance_generate_video - Removed
seedance_generate_video_from_image - Removed
seedance_get_task - Removed
seedance_get_tasks_batch - Removed
seedance_list_actions - Removed
seedance_list_models - Removed
seedance_list_resolutions
2 tool updates
v0.1.1- Changed
seedance_generate_video2 fields changed- changed
Input schema / properties / model / descriptionPrevious value: -"Model version to use. Options: 'doubao-seedance-1-5-pro-251215' (newest flagship, supports audio), 'doubao-seedance-1-0-pro-250528' (standard, default), 'doubao-seedance-1-0-pro-fast-251015' (fast, cost-optimized), 'doubao-seedance-1-0-lite-t2v-250428' (lightweight text-to-video), 'doubao-seedance-1-0-lite-i2v-250428' (lightweight image-to-video)."New value: +"Model version to use. Options: 'doubao-seedance-2-0-260128' (latest generation quality model), 'doubao-seedance-2-0-fast-260128' (latest generation fast model), 'doubao-seedance-1-5-pro-251215' (newest flagship, supports audio), 'doubao-seedance-1-0-pro-250528' (standard, default), 'doubao-seedance-1-0-pro-fast-251015' (fast, cost-optimized), 'doubao-seedance-1-0-lite-t2v-250428' (lightweight text-to-video), 'doubao-seedance-1-0-lite-i2v-250428' (lightweight image-to-video)." - changed
Input schema / properties / model / enumPrevious value: -[ - "doubao-seedance-1-5-pro-251215", - "doubao-seedance-1-0-pro-250528", - "doubao-seedance-1-0-pro-fast-251015", - "doubao-seedance-1-0-lite-t2v-250428", - "doubao-seedance-1-0-lite-i2v-250428" -]New value: +[ + "doubao-seedance-1-5-pro-251215", + "doubao-seedance-1-0-pro-250528", + "doubao-seedance-1-0-pro-fast-251015", + "doubao-seedance-1-0-lite-t2v-250428", + "doubao-seedance-1-0-lite-i2v-250428", + "doubao-seedance-2-0-260128", + "doubao-seedance-2-0-fast-260128" +]
- Changed
seedance_generate_video_from_image2 fields changed- changed
Input schema / properties / model / descriptionPrevious value: -"Model version to use. For image-to-video, consider 'doubao-seedance-1-0-lite-i2v-250428' for lightweight I2V, or any Pro model for higher quality."New value: +"Model version to use. Use 'doubao-seedance-2-0-260128' for latest generation quality, 'doubao-seedance-2-0-fast-260128' for latest generation speed, For image-to-video, consider 'doubao-seedance-1-0-lite-i2v-250428' for lightweight I2V, or any Pro model for higher quality." - changed
Input schema / properties / model / enumPrevious value: -[ - "doubao-seedance-1-5-pro-251215", - "doubao-seedance-1-0-pro-250528", - "doubao-seedance-1-0-pro-fast-251015", - "doubao-seedance-1-0-lite-t2v-250428", - "doubao-seedance-1-0-lite-i2v-250428" -]New value: +[ + "doubao-seedance-1-5-pro-251215", + "doubao-seedance-1-0-pro-250528", + "doubao-seedance-1-0-pro-fast-251015", + "doubao-seedance-1-0-lite-t2v-250428", + "doubao-seedance-1-0-lite-i2v-250428", + "doubao-seedance-2-0-260128", + "doubao-seedance-2-0-fast-260128" +]
7 tool updates
v0.1.0- First observed
seedance_generate_video - First observed
seedance_generate_video_from_image - First observed
seedance_get_task - First observed
seedance_get_tasks_batch - First observed
seedance_list_actions - First observed
seedance_list_models - First observed
seedance_list_resolutions
TDQS
Scored across 7 tools
Each tool serves a clearly distinct purpose: listing models, listing resolutions, listing actions, querying a single task, querying multiple tasks, generating from text, and generating from images. There is no overlap or ambiguity in tool boundaries.
All tools follow a consistent seedance_ prefix with snake_case verb_noun naming (e.g., seedance_list_models, seedance_generate_video_from_image). The pattern is uniform and predictable across the entire set.
With 7 tools, the set is well-scoped for a video generation API: three discovery tools, two status-query tools, and two generation methods. Each tool earns its place without redundancy or bloat.
The server covers the full video-generation workflow: model and resolution discovery, two generation modes, and both single and batch status retrieval. No essential operations (e.g., cancel, delete) seem necessary for the domain, and the existing tools provide all needed functionality.
Maintenance
Related MCP Connectors
AI video, images, music & SFX: Seedance 2.5, Veo 3.1, Kling 3.0, Nano Banana Pro, 20+ models.
- KubflowOAuthai.kubflow
Create AI images, videos and audio with Veo, Kling, Seedance, Nano Banana, Suno and more.
AI image, video, voice and music generation over MCP, routed to Veo 3.1, Seedance 2.5 and more.
Best Image and video generation: 20+ models (Kling, Seedance, Veo, NB, FLUX.2), OAuth, pay-per-use.
Related MCP Servers
- AlicenseAqualityBmaintenanceByteDance Seedream AI image generation and editing (style transfer, background change, virtual try-on) with multiple models, multi-resolution up to 4K, and streaming delivery.7861 PyPI3MIT
- AlicenseAqualityDmaintenanceExposes Volcengine ARK Seedance 2.0 video generation capabilities via MCP tools, enabling text-to-video, image-to-video, and multimodal reference generation locally.39MIT
- AlicenseBqualityAmaintenanceProvider-neutral short-form AI video toolkit for agents: Sora, Gemini Veo, xAI/Grok and Seedance.577 npm2MIT
- AlicenseBqualityCmaintenanceGenerates videos using bytedance/seedance-2 models on Polza.ai, supporting text-to-video and image-to-video with polling for completion.41MIT