Skip to main content
Glama
runapi-ai

z-image-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

text_to_image

Generate images from text prompts with Z Image models via RunAPI, returning a task ID, status, and output URLs for tracking and retrieval.

Instructions

Create a Z Image 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_ratioYesDeclared type: string. Known values: "1:1", "4:3", "3:4", "16:9", "9:16".
callback_urlNoDeclared type: string.
poll_interval_msNo
enable_safety_checkerNoDeclared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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\"."
    • removedInput schema / properties / aspect_ratio / enum
      Removed value: -[
-  "1:1",
-  "4:3",
-  "3:4",
-  "16:9",
-  "9:16"
-]
    • addedInput schema / properties / callback_url
      Added value: +{
+  "description": "Declared type: string.",
+  "type": "string"
+}
    • addedInput schema / properties / enable_safety_checker
      Added value: +{
+  "description": "Declared type: boolean.",
+  "type": "boolean"
+}
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "z-image"
-]
    • 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: -1000
    • removedInput schema / properties / prompt / minLength
      Removed value: -1
    • 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 are provided, so the description carries the full behavioral burden. It usefully discloses that this is an async task-creating operation and what it returns (task id, status, output URLs), which substitutes for the missing output schema, but says nothing about credit/cost implications, auth requirements, or how the safety checker or callback affect execution.

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 action and resource, and the second sentence earns its place by describing the return payload in the absence of an output schema. No filler or redundancy.

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 an 8-parameter creation tool with no annotations and no output schema, the description covers the return shape but omits cost, auth, polling behavior, and callback mechanics. It is minimally adequate but leaves an agent unable to reason about pricing or the async lifecycle beyond the bare return fields.

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?

Description adds no parameter meaning at all. Schema coverage is a solid 75% and the schema documents wait, model, and aspect_ratio, so the baseline of 3 applies, but weak entries like prompt ('Declared type: string.') and undocumented params such as callback_url, enable_safety_checker, and poll_interval_ms leave the description contributing nothing on this dimension.

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 Z Image task on RunAPI (text to image),' which clearly distinguishes it from the read-oriented siblings get_task and check_pricing. The branding 'Z Image task' is opaque, but the '(text to image)' gloss makes the core function unambiguous.

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 when-to-use guidance and no routing to alternatives. With a get_task sibling present, the agent gets no guidance on when to rely on the `wait` flag versus fetching later via get_task, nor any mention of cost-checking via check_pricing before invoking.

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