Skip to main content
Glama

flux_get_task

Check the status of an image generation task and retrieve the resulting image URLs and metadata.

Instructions

Query the status and result of a Flux image generation task.

Use this to check if a generation 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 used async callback and want to check results later
- The initial generation returned a task_id without immediate results

Returns:
    Task status and generation result including image URLs.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It correctly indicates this is a read-only query with no destructive effects, and mentions return content (image URLs and metadata). However, it does not disclose any rate limits, caching behavior, or error conditions, which are helpful for a polling tool.

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?

The description is well-structured with a clear initial sentence, a bullet list of use cases, and a returns summary. It is concise without being terse, with no redundant information. Minor improvement could be removing the 'Returns:' line if output schema covers it, but still efficient.

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

Completeness4/5

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

Given the tool has one simple parameter and an output schema (context confirms its existence), the description covers the essential purpose and usage context. It explains when to use and what to expect, making it complete for an agent to understand when and how to invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with only one parameter (task_id). The schema description is already rich, specifying it comes from generation or edit tools. The description adds context by linking task_id to async workflows. This combination provides sufficient semantic clarity beyond the schema alone.

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?

The description clearly states 'Query the status and result of a Flux image generation task,' providing a specific verb and resource. It differentiates from sibling tools like flux_get_tasks_batch by focusing on a single task, and from generation tools by being a query operation.

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?

The description includes a 'Use this when' section listing four specific scenarios (check completion, retrieve URLs, async callback, delayed results). While it does not explicitly mention when not to use or alternatives like flux_get_tasks_batch, the guidance is clear and actionable.

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

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