Skip to main content
Glama

seedream_get_task

Retrieve the status, result image URLs, and metadata of a Seedream image generation or edit task using its task ID.

Instructions

Query the status and result of a Seedream image generation or edit task.

Use this to check if a generation/edit is complete and retrieve the resulting
image URLs and metadata.

Use this when:
- You want to check if an image generation has completed
- You need to retrieve image URLs from a previous generation
- You want to get the full details of a generated/edited image

Returns:
    Task status and image information including URLs, prompts, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task ID returned from a generation or edit request. This is the 'task_id' field from any seedream_generate_image or seedream_edit_image tool response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but description explains it returns status, URLs, prompts, metadata. It does not mention destructive behavior, appropriate for a polling tool. No contradictions.

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 header, bullet points, and Returns section. Each sentence is meaningful; no redundancy. Slightly verbose but within reason.

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?

For a single-parameter polling tool with an output schema, the description covers the necessary aspects: how to use it, what it returns, and the source of the parameter. No gaps.

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 coverage is 100% and already describes task_id as returned from generation/edit. Description adds context about usage but does not significantly extend schema information.

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?

Description clearly states verb 'Query' and resource 'status and result of a Seedream image generation or edit task'. It distinguishes from siblings like seedream_generate_image and seedream_get_tasks_batch by specifying it checks a single task.

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

Usage Guidelines4/5

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

Provides explicit 'Use this when' scenarios: checking completion, retrieving URLs, getting details. Does not explicitly exclude batch retrieval but context from sibling names makes it clear.

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/SeedreamMCP'

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