Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Localize a static ad into other languages

localize_ad

Translate the on-image text of a finished static ad into up to 5 languages, preserving the same picture, layout, typeface, colours, logo and product.

Instructions

Translate the on-image text of ONE finished static ad into other languages and keep everything else: same picture, layout, typeface, colours, logo and product. Pass image and languages (up to 5, e.g. ["Spanish", "German", "French (Canada)"]). The ad's text is read (3 credits), translated the way a native copywriter in each market would write it (brand and product names, URLs and prices kept as written), then one image edit per language; each output is proofread and flagged (textCheck) if the words do not match, never silently re-rendered. 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. Priced before it runs. For a VIDEO use dub_video.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesthe finished static ad: URL, Library item URL, upload_file URL or local path
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)
languagesYestarget languages, by name

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. Addedv0.1.272

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive) by disclosing the credit model (3 credits to read, extra charge per edit and for product lookup), the proofreading/textCheck flagging behavior, the promise never to silently re-render, and the product-photo/label re-print logic. Pricing is stated to occur before the run, which is material for an open-world, billable mutation.

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 the core action and scoping before the pricing and label-handling detail. It is dense and contains one long run-on sentence stacking credits, translation behavior and per-language edits, but essentially every clause carries operational information an agent needs.

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?

With no output schema, the description still conveys what comes back (one image edit per language, each proofread and flagged via textCheck) and the billing behavior. It stops short of describing the exact return shape or how textCheck flags are surfaced, but for a 3-parameter tool this is close to complete.

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 the schema already carries most parameter documentation, but the description adds real meaning: concrete language-format examples showing locale variants (['Spanish', 'German', 'French (Canada)']) where the schema only says 'by name', and a plain-language restatement of what fixLabel:false disables (no product lookup, no label check, no re-print).

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?

States a specific verb (translate/localize) and resource (the on-image text of ONE finished static ad) with an explicit scope constraint ('keep everything else: same picture, layout, typeface, colours, logo and product'). It also names the sibling it is not ('For a VIDEO use dub_video'), letting an agent separate it from dub_video, clone_static and remix_static without opening a schema.

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?

Gives clear usage context (one finished static ad, up to 5 target languages) and an explicit alternative for the video case. It does not, however, contrast itself against the other static-ad siblings (clone_static, remix_static, multiply_ad), which an agent choosing between ad-creation tools would need.

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