Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Edit an image

edit_image

Modify an existing image in place using a plain-language instruction while preserving composition, aspect ratio, and untouched text. Supports removing text or objects.

Instructions

EDIT an existing image in place with a plain-language instruction and keep everything else: 'make the headline bigger', 'add our logo bottom right', 'swap the background for a kitchen', 'remove the person on the left', 'erase all the text'. Pass image (URL, Library item, upload_file URL or local path) and instruction. The same edit the web Studio's Edit runs: composition, aspect ratio, people and every untouched line of text stay as they are; the saved brand's real name and website are pinned so an added line never invents one, and the brand's real logo is attached when the instruction asks for the logo. Set removal:true when the edit STRIPS text, branding or an object, so nothing branded is put back. When the saved brand has a product photo and the ad shows that product, the photo rides with the edit and the product's label is read and checked against it: re-printed from the photo only when it came out wrong (the check alone is charged when it is right; one small extra charge finds the product first). fixLabel:false turns that off. For a precise region, pass mask (see generate_image). One image edit's credits; returns the new image URL. For a new image from a prompt use generate_image; to rebuild a competitor's ad for your brand use clone_static.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maskNooptional mask image (URL or local path) marking the region to change: transparent = change, or white = change on an opaque mask
imageYesthe image to edit: URL, Library item URL, upload_file URL or local path
dryRunNotrue = return the exact credits this edit reserves and render nothing
removalNotrue when the edit REMOVES text, branding, a logo, a watermark, a person or an object, so the brand name and logo are not re-added
fixLabelNofalse = leave the product label exactly as rendered: no product lookup, no label check, no re-print (default on when the ad shows the brand’s saved product)
instructionYesthe change to make, in plain words (pass the user’s own words for a removal or plain photo edit)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.366
    • addedInput schema / properties / fixLabel
      Added value: +{
+  "description": "false = leave the product label exactly as rendered: no product lookup, no label check, no re-print (default on when the ad shows the brand’s saved product)",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.1.320
    • addedInput schema / properties / dryRun
      Added value: +{
+  "description": "true = return the exact credits this edit reserves and render nothing",
+  "type": "boolean"
+}
  3. Addedv0.1.272

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: what is preserved (composition, aspect ratio, people, untouched text), that the brand name/website are pinned and the brand logo attached, the semantics of removal:true, the product-label re-print/check behavior with its charging model, and 'One image edit's credits; returns the new image URL.' This is rich disclosure of side effects and costs.

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?

Front-loaded with purpose and routed alternatives, and every clause carries behavioral information. However the product-photo/label sentence is dense and nested, and the overall block could be tightened; some clauses require re-reading despite earning their place.

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

Completeness5/5

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

For a 6-param, no-output-schema mutation tool, the description covers preservation rules, credit cost, return value (new image URL), and brand/product safety behavior. Nothing an agent needs to invoke it correctly is missing.

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%, so baseline is 3, but the description adds real meaning beyond the schema: removal:true 'so nothing branded is put back' and fixLabel:false disabling product lookup/check/re-print clarify intent beyond the field text. It also frames mask as the precise-region control.

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 a specific verb+resource ('EDIT an existing image in place') plus a plain-language instruction, and closes by naming both sibling alternatives (generate_image, clone_static). An agent can distinguish this from generate_image/clone_static without opening any schema.

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?

Explicit routing: 'For a new image from a prompt use generate_image; to rebuild a competitor's ad for your brand use clone_static.' It also states the conditional for removal:true and fixLabel:false and points to mask usage, giving clear when/when-not guidance.

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

Deploy Server

Other Tools