Skip to main content
Glama

advanced_edit

Edit images with AI: remove or insert objects, expand canvas, swap backgrounds, transfer styles, or create product images.

Instructions

Advanced image editing with specialized modes (requires Vertex AI).

This feature requires Google Cloud Vertex AI credentials. Set GOOGLE_CLOUD_PROJECT environment variable to enable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesEdit instruction
edit_modeYesOne of: inpaint_removal, inpaint_insertion, outpaint, background_swap, style_transfer, product_image
mask_pathNoOptional mask image for inpainting operations
image_pathYesPath to the image to edit
output_formatNoOutput format (png, jpeg, webp)png
output_filenameNoCustom output filename (optional)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states requirements (Vertex AI) but does not explain error behavior, side effects, image handling, or limitations. Lacks depth for a complex tool.

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 concise sentences, front-loaded with purpose and requirement. No redundant information. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description lacks operational context: no explanation of edit modes, mask usage, or expected outcomes. For a tool with 6 parameters and complex modes, this is insufficient.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the parameter descriptions already in the schema. It does not explain param relationships or typical usage patterns.

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?

The description states 'Advanced image editing with specialized modes,' which clearly indicates the tool's purpose and distinguishes it from simpler editing tools like edit_image. However, it does not explicitly contrast with siblings, so it's not a full 5.

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?

The description mentions prerequisites (Vertex AI credentials, environment variable) but provides no guidance on when to use this tool versus alternatives like edit_image or transform_image. No when-not-to-use or selection criteria.

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/Tehnolabs/pixelforge-mcp'

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