Skip to main content
Glama

Outil.io

Edit image

edit_image

Retoucher un logo, pictogramme ou visuel sur fond uni dans la galerie. removeBackground:true rend le fond uni transparent, foregroundColor:"#FFFFFF" rend blanc le motif (par exemple du texte). Combiner les deux dans un appel. sourceColor permet de ne recolorer que la couleur du texte dans un logo multicolore. Accepte assetId ou url (dont /uploads/… ou HTTPS public). format:"svg" vectorise le motif en vrais tracés et fournit une URL de téléchargement, avec ou sans retouche (logos et illustrations simples, palette colors 2–16). Par défaut, enregistre un PNG dans la galerie et renvoie son URL. L’original et les pages restent inchangés. Pour un logo déjà sur une page, lire son URL puis remplacer uniquement sa source (content pour un bloc image, logoUrl pour une navigation) par l’URL renvoyée avec apply_page_changes ou edit_live_page. Si le logo est du vrai texte, modifier directement sa couleur et le fond du bloc. Détourage de fonds unis uniquement.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "edit_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL HTTPS de l’image, chemin /uploads/… ou /template-assets/…
colorsNoMaximum de couleurs du tracé SVG. Défaut : 8.
formatNoPNG retouché ou SVG en vrais tracés vectoriels. Choisir SVG pour vectoriser une image.
assetIdNoID du média dans la galerie du projet
filenameNo
sourceColorNoCouleur originale à recolorer pour préserver les autres couleurs
backgroundColorNoCouleur du fond uni si connue, sinon détection par les bords
foregroundColorNoNouvelle couleur du motif ou du texte. Blanc : #FFFFFF
removeBackgroundNoRendre un fond uni transparent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description usefully confirms the non-destructive behavior ('L'original et les pages restent inchangés') plus the default side effect of saving a PNG into the gallery and returning its URL. It discloses that SVG mode produces a downloadable URL and that remote HTTPS URLs are accepted, though it says nothing about permissions, size limits or failure modes.

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 paragraph is front-loaded with the purpose and the main option combinations before moving to the page-integration workflow, and nearly every sentence carries actionable detail. It is dense and slightly repetitive about solid-background-only masking, and a short bulleted split of options versus follow-up steps would read better, but there is little wasted text.

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?

For a nine-parameter tool with no output schema, the description covers what is returned (gallery PNG URL or SVG download URL) and how to consume the result on a page. The gap is the undocumented filename parameter and no guidance on behavior when a source is invalid or a background is not uniform beyond the stated limitation.

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?

With schema coverage at 89% the baseline would be 3, but the description adds genuine meaning beyond the schema: it explains the interaction between removeBackground and foregroundColor, the purpose of sourceColor for preserving other colors, the acceptable 2–16 palette range for vectorization, and the default PNG behavior. The only unexplained parameter is filename.

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 names a specific action and target – retouching a logo, pictogram or visual on a solid background in the gallery – and immediately bounds the scope with 'Détourage de fonds unis uniquement'. It also separates its role from downstream tools by pointing to apply_page_changes / edit_live_page for applying results to a page, so the agent can tell what this tool does and does not do.

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?

It gives explicit when-to-use rules: combine removeBackground with foregroundColor to make a motif white and the background transparent, use sourceColor only to recolor the text color in a multicolor logo, use format:"svg" when vectorization is wanted, and edit real text directly rather than retouching it. It also names the alternative workflow (read the page's logo URL, then replace only the source via apply_page_changes or edit_live_page) and states the exclusion for non-solid backgrounds.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.