Skip to main content
Glama

flux_edit_image

Edit existing images using text prompts to modify objects, change styles, or transform backgrounds. Uses Flux kontext models for context-aware editing and precise image modifications.

Instructions

Edit an existing image using Flux with a text prompt.

This allows you to modify an existing image based on a text description. The kontext models (flux-kontext-pro, flux-kontext-max) are specifically designed for high-quality image editing and style transfer.

Use this when:

  • You want to modify or transform an existing image

  • You want to change specific elements in an image

  • You want to apply style changes or artistic effects

  • You want to add, remove, or replace objects in an image

For generating new images from scratch, use flux_generate_image instead.

Returns: Task ID and edited image information including URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of how to edit the image. Be specific about what changes to make. Examples: 'Change the background to a sunset beach', 'Add sunglasses to the person', 'Make it look like a watercolor painting', 'Replace the car with a bicycle'
image_urlYesURL of the image to edit. Must be a direct image URL (JPEG, PNG, etc.), not a web page containing an image.
modelNoFlux model to use for editing. Recommended models for editing: - flux-kontext-pro: Best for context-aware editing and style transfer (recommended) - flux-kontext-max: Maximum context for complex edits - flux-dev: Basic editing support Other models also support editing but kontext models give best results.flux-kontext-pro
sizeNoOutput image size. For kontext models: aspect ratios like '1:1', '16:9'. For other models: pixel dimensions like '1024x1024'.
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses key behavioral traits: mentions Task ID return (implying async operation), notes kontext models are specifically designed for high-quality editing, and clarifies output includes URLs. Does not explicitly state whether operation is destructive or mention rate limits.

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?

Well-structured with clear sections (purpose, model details, use cases, alternative, returns). Front-loaded with primary action. Minor redundancy between first two sentences ('Edit... using Flux' vs 'allows you to modify... based on text description'), but efficient overall.

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?

Appropriately complete for a 5-parameter AI editing tool. Despite existence of output schema, description summarizes return values (Task ID, URLs). Addresses sibling relationship critical for this tool suite. Lacks only safety/destructive details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds value by emphasizing that kontext models (flux-kontext-pro/max) are 'specifically designed for high-quality image editing' versus other models, guiding model parameter selection beyond raw schema enum.

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?

Opens with specific verb+resource+mechanism ('Edit an existing image using Flux with a text prompt'). Explicitly distinguishes from sibling flux_generate_image ('For generating new images from scratch, use flux_generate_image instead').

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

Usage Guidelines5/5

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

Contains explicit 'Use this when:' section with four specific scenarios (modify/transform, change elements, style changes, add/remove objects). Clearly states the alternative tool for non-editing use cases.

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/AceDataCloud/MCPFlux'

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