@runapi.ai/gpt-4o-image-mcp

Official

Overview Schema Source Related Servers Discussions Admin

text_to_image

Generate images from text prompts by creating GPT-4o Image tasks on RunAPI, returning task IDs, statuses, and output URLs.

Instructions

Create a GPT-4o Image task on RunAPI (text to image). Returns a task id, status, and output URLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "aspect_ratio": "<aspect_ratio>"
    },
    "name": "text_to_image"
  }
}

Input Schema

Name	Required	Description
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	No	Declared type: string.
`mask_url`	No	Declared type: string.
`timeout_ms`	No
`aspect_ratio`	Yes	Declared type: string. Known values: "1:1", "3:2", "2:3".
`callback_url`	No	Declared type: string.
`output_count`	No	Declared type: integer. Known values: 1, 2, 4.
`poll_interval_ms`	No
`source_image_urls`	No	Declared type: array.
`enable_prompt_expansion`	No	Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.2.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / aspect_ratio / description
```
Added value: +"Declared type: string. Known values: \"1:1\", \"3:2\", \"2:3\"."
```
- removedInput schema / properties / aspect_ratio / enum
```
Removed value: -[
-  "1:1",
-  "3:2",
-  "2:3"
-]
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / enable_prompt_expansion / description
```
Added value: +"Declared type: boolean."
```
- addedInput schema / properties / mask_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "gpt-4o-image"
-]
```
- addedInput schema / properties / output_count / description
```
Added value: +"Declared type: integer. Known values: 1, 2, 4."
```
- removedInput schema / properties / output_count / enum
```
Removed value: -[
-  1,
-  2,
-  4
-]
```
- 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."
```
- addedInput schema / properties / source_image_urls / description
```
Added value: +"Declared type: array."
```
- removedInput schema / properties / source_image_urls / maxItems
```
Removed value: -5
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed5 schema fields changedv0.1.7Jul 22, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / enable_prompt_expansion
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / mask_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / source_image_urls
```
Added value: +{
+  "items": {},
+  "maxItems": 5,
+  "type": "array"
+}
```
First observedv0.1.0Jun 24, 2026

TDQS

B3.3/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, and it partially delivers by disclosing the return shape (task id, status, output URLs), which is genuinely useful since no output schema exists. However, it says nothing about the asynchronous nature of the task, how the 'wait' and 'callback_url' parameters change blocking behavior, or any auth/rate-limit constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the action front-loaded and the return contract second. Nothing is wasted and there is no filler.

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 11-parameter tool with no annotations and no output schema, the description covers the action and the return payload but omits the operational semantics that matter most: that this enqueues an async task, and how 'wait', 'timeout_ms', and 'callback_url' interact. Adequate but noticeably incomplete.

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 82%, so the baseline is 3. The description adds no parameter-level meaning at all, and several schema descriptions are just 'Declared type: string' filler, so the agent gets no extra help on prompt, mask_url, or callback_url semantics.

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?

Names a specific verb and resource ('Create a GPT-4o Image task on RunAPI') and disambiguates the modality with '(text to image)', which separates it from siblings like get_task and check_pricing. It stops short of explicitly naming an alternative for retrieval, but the action is 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?

There is no when-to-use guidance, no mention of prerequisites, and no indication of how this relates to get_task for checking results or to login for authentication. The agent must infer the entire workflow from the sibling names.

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

Deploy Server