Skip to main content
Glama

seedance_get_task

Check video generation task status and retrieve completed video URLs, thumbnails, and metadata from the MCPSeedance server.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task ID returned from a generation request. This is the 'task_id' field from any seedance_generate_* tool response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses task lifecycle statuses (running/succeeded/failed) and return value structure beyond schema; lacks only operational details like idempotency or rate limits.

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?

Well-structured with front-loaded purpose, bullet points for usage scenarios, and clear status definitions; 'Returns' section slightly redundant given output schema exists but appropriately brief.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully complete for a single-parameter status retrieval tool; covers purpose, usage contexts, status semantics, and return values without over-explaining schema-covered details.

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?

Schema has 100% coverage with complete task_id description; tool description adds no parameter-specific semantics but meets baseline expectation given schema quality.

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?

Clear specific verb ('Query') + resource ('status and result of a video generation task'), explicitly distinguishes from generation siblings by stating this retrieves results from previous generation requests.

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

Usage Guidelines5/5

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

Explicit 'Use this when:' section with three specific scenarios (checking completion, retrieving URLs, getting full details) plus task status definitions that implicitly guide polling behavior vs. generation tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/MCPSeedance'

If you have feedback or need assistance with the MCP directory API, please join our Discord server