Skip to main content
Glama

OpenAI Images Edit

openai-images-edit
Read-only

Edit images by providing a prompt and optional mask to inpaint, outpaint, or composite using OpenAI models, supporting 1 to 16 inputs.

Instructions

Edit images (inpainting, outpainting, compositing) from 1 to 16 inputs using OpenAI gpt-image-1.5 (default) or gpt-image-1. Returns MCP CallToolResult with content[] (ResourceLink or ImageContent based on tool_result param) and structuredContent (OpenAI ImagesResponse format with data[].url, data[].path, or data[].b64_json based on response_format param).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesAbsolute image path, base64 string, or HTTP(S) URL to edit, or an array of such values (1-16 images).
promptYesA text description of the desired edit. Max 32000 chars.
maskNoOptional absolute path, base64 string, or HTTP(S) URL for a mask image (png < 4MB, same dimensions as the first image). Fully transparent areas indicate where to edit.
modelNogpt-image-1.5
nNoNumber of images to generate (1-10).
qualityNoQuality (high, medium, low). Default: high.high
sizeNoSize of the generated images. Default: 1024x1536.1024x1536
userNoOptional user identifier for OpenAI monitoring.
tool_resultNoControls content[] shape: 'resource_link' (default) emits ResourceLink items, 'image' emits base64 ImageContent blocks.resource_link
response_formatNoControls structuredContent shape: 'url' (default) emits data[].url, 'path' emits data[].path, 'b64_json' emits data[].b64_json.url
Behavior4/5

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

The description details the output format (CallToolResult with content[] and structuredContent) and the role of tool_result and response_format params, adding value beyond annotations which already indicate read-only behavior.

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?

The description is a single sentence but packs essential info efficiently; however, it could be better structured for readability.

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?

Given the rich schema and no output schema, the description adequately explains the output structure and main purpose, though it omits details like mask constraints.

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?

With 90% schema description coverage, the description adds only marginal value (e.g., listing edit types and model names). Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states 'Edit images (inpainting, outpainting, compositing)' with specific models and input counts, distinguishing it from the sibling 'openai-images-generate' tool.

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?

While not explicitly stating when not to use, the description implies usage for image editing tasks and the sibling list shows relevant alternatives, providing clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/strato-space/media-gen-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server