Skip to main content
Glama
runapi-ai

Flux MCP Server

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

text_to_image

Create Flux image generation tasks on RunAPI from text prompts and get task IDs, status, and output URLs.

Instructions

Create a Flux task on RunAPI (text to image). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
promptYesDeclared type: string.
timeout_msNo
aspect_ratioNoDeclared type: string. Known values: "1:1", "4:3", "3:4", "16:9", "9:16", "3:2", "2:3".
callback_urlNoDeclared type: string.
output_countNoDeclared type: integer. Known values: 1.
poll_interval_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.2.0
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • addedInput schema / properties / aspect_ratio / description
      Added value: +"Declared type: string. Known values: \"1:1\", \"4:3\", \"3:4\", \"16:9\", \"9:16\", \"3:2\", \"2:3\"."
    • removedInput schema / properties / aspect_ratio / enum
      Removed value: -[
-  "1:1",
-  "4:3",
-  "3:4",
-  "16:9",
-  "9:16",
-  "3:2",
-  "2:3"
-]
    • addedInput schema / properties / callback_url / description
      Added value: +"Declared type: string."
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "flux-2-klein",
-  "flux-dev",
-  "flux-pro"
-]
    • addedInput schema / properties / output_count / description
      Added value: +"Declared type: integer. Known values: 1."
    • removedInput schema / properties / output_count / enum
      Removed value: -[
-  1
-]
    • changedInput schema / properties / output_count / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / poll_interval_ms / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / prompt / description
      Added value: +"Declared type: string."
    • removedInput schema / properties / prompt / maxLength
      Removed value: -5000
    • removedInput schema / properties / prompt / minLength
      Removed value: -3
    • addedInput schema / properties / timeout_ms / maximum
      Added value: +9007199254740991
  2. First observedv0.1.0

TDQS

B3.2/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 does disclose the async task-based nature and the return shape (task id, status, output URLs), which is meaningful. But it omits auth requirements, cost implications, and how the 'wait' polling behavior affects the call.

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?

Two short sentences, front-loaded with the core action and followed by the return values. Efficient with no wasted text, though extremely terse.

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

Completeness3/5

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

There is no output schema and no annotations, so the description must compensate; it partially does by naming return fields. However, with 8 parameters and an async task lifecycle, it should explain at least the wait/polling semantics and how to retrieve results afterward.

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 description coverage is 75%, near the high-coverage baseline, so the schema does most of the work. The description adds nothing about the 8 parameters (prompt, model, aspect_ratio, callback_url, timeout_ms, poll_interval_ms, output_count, wait) beyond the text-to-image framing.

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 ('Create') and resource ('Flux task') plus a clarifying parenthetical ('text to image'). It is distinguishable from get_task and remix_image by name and scope, but it does not explicitly contrast with the sibling remix_image, which also involves image generation.

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

Usage Guidelines2/5

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

No guidance on when to use this versus remix_image or get_task, and no prerequisites or context about the RunAPI task workflow. The agent must infer the use case from the name alone.

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