Skip to main content
Glama
AceDataCloud

FluxMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

flux_get_task

Check the status and retrieve results of a Flux image or video generation task using its task ID. Returns completed task details including image/video URLs and metadata.

Instructions

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

Use this to check if a generation is complete and retrieve the resulting
image/video 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, flux_edit_image or a FLUX video tool response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.12
    • changedInput schema / properties / task_id / description
      Previous value: -"The 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."New value: +"The task ID returned from a generation or edit request. This is the 'task_id' field from any flux_generate_image, flux_edit_image or a FLUX video tool response."
  2. Addedv0.1.3
  3. Removedv0.1.2
  4. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It discloses the async polling role and that results contain image/video URLs and metadata, but says nothing about the possible task states, whether results expire, or auth requirements — real gaps for a no-annotation tool, though the core behavior is conveyed.

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?

Front-loaded purpose sentence followed by scannable bullets; every line is relevant. Minor redundancy in the 'Returns' block, which restates output already covered by the output schema.

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?

For a one-parameter read tool with a full output schema and 100% schema coverage, this is nearly complete. The redundant Returns section and the missing batch-sibling routing are the only shortfalls.

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 the single task_id parameter is fully documented in the schema, including its origin fields. The description adds no parameter detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Query the status and result of a Flux image or video generation task.' Clear that this is a polling/retrieval tool distinct from the generation siblings, but it never differentiates itself from flux_get_tasks_batch, the obvious plural counterpart.

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?

Four explicit when-to-use bullets cover the polling scenarios (checking completion, retrieving URLs, async callback follow-up, task_id with no immediate result). No when-not-to-use guidance and no pointer to flux_get_tasks_batch for multi-task retrieval, so it stops short of a 5.

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

Deploy Server

Other Tools