Skip to main content
Glama
runapi-ai

RunAPI Qwen Image MCP Server

Official
by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edit_image

Edit a source image from a public URL using a text prompt and RunAPI; creates a Qwen Image task and returns task ID, status, and output URLs.

Instructions

Create a Qwen Image task on RunAPI (edit image). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoInteger seed for reproducible results. Declared type: integer.
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
promptYesEdit instruction for the source image. Declared type: string.
timeout_msNo
aspect_ratioNoOutput aspect ratio. Declared type: string. Known values: "1:1", "3:4", "9:16", "4:3", "16:9".
callback_urlNoWebhook URL for asynchronous task updates. Declared type: string.
output_formatNoOutput image format. Declared type: string. Known values: "png", "jpeg".
poll_interval_msNo
source_image_urlYesPublic HTTPS source image URL (JPEG, PNG, or WebP; maximum 10 MB). Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.2.0
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedInput schema / properties / aspect_ratio / description
      Previous value: -"Output aspect ratio."New value: +"Output aspect ratio. Declared type: string. Known values: \"1:1\", \"3:4\", \"9:16\", \"4:3\", \"16:9\"."
    • removedInput schema / properties / aspect_ratio / enum
      Removed value: -[
-  "1:1",
-  "3:4",
-  "9:16",
-  "4:3",
-  "16:9"
-]
    • changedInput schema / properties / callback_url / description
      Previous value: -"Webhook URL for asynchronous task updates."New value: +"Webhook URL for asynchronous task updates. Declared type: string."
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "qwen-image-edit-image"
-]
    • changedInput schema / properties / output_format / description
      Previous value: -"Output image format."New value: +"Output image format. Declared type: string. Known values: \"png\", \"jpeg\"."
    • removedInput schema / properties / output_format / enum
      Removed value: -[
-  "png",
-  "jpeg"
-]
    • addedInput schema / properties / poll_interval_ms / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / prompt / description
      Previous value: -"Edit instruction for the source image."New value: +"Edit instruction for the source image. Declared type: string."
    • removedInput schema / properties / prompt / maxLength
      Removed value: -2000
    • removedInput schema / properties / prompt / minLength
      Removed value: -1
    • changedInput schema / properties / seed / description
      Previous value: -"Integer seed for reproducible results."New value: +"Integer seed for reproducible results. Declared type: integer."
    • changedInput schema / properties / seed / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / source_image_url / description
      Previous value: -"Public HTTPS source image URL (JPEG, PNG, or WebP; maximum 10 MB)."New value: +"Public HTTPS source image URL (JPEG, PNG, or WebP; maximum 10 MB). Declared type: string."
    • addedInput schema / properties / timeout_ms / maximum
      Added value: +9007199254740991
  2. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the async task contract ('returns a task id, status, and output URLs'), which implies a polling/retrieval flow, but omits the wait/polling default behavior, auth requirements, and rate limits that matter for a 10-param task-based 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?

Two short sentences, front-loaded with the core action and ending with the return contract. No filler; 'on RunAPI' is mild vendor noise but the rest earns its place.

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?

For a 10-parameter asynchronous task tool with no annotations, the description is thin: it never explains the wait/polling parameter or the async lifecycle, and gives no usage context. It partially compensates by stating return values in the absence of an output schema, but leaves meaningful 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 description coverage is 80%, so the schema already documents nearly all parameters (prompt, seed, wait, model, aspect_ratio, etc.). The description adds no parameter meaning beyond that, so the baseline of 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 and resource ('Create a Qwen Image task ... edit image') and clarifies it returns a task id, status, and output URLs. It distinguishes itself from text_to_image by naming 'edit image', though it doesn't explicitly differentiate from remix_image, which is a similar transformation sibling.

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 text_to_image, remix_image, or the synchronous alternatives. It doesn't mention prerequisites (e.g., needing a public source image URL) or when to prefer get_task for retrieval. The agent must infer usage 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