Skip to main content
Glama
Hermoso

Hermoso

Official

Clone a static ad

clone_static

Rebuilds a supplied static ad image into an on-brand version with the same layout and composition, swapping in your product, colors, logo and voice while removing the source branding.

Instructions

Use this when the user wants their own version of a static (image) ad they like, a competitor's or any reference. It rebuilds it on-brand: SAME layout, composition and energy, but the user's product, brand colours, logo and voice, with every trace of the source brand removed. Pass imageUrl = the static ad image to clone. Uses the saved brand (brandId picks another profile, like use_brand). IMAGES ONLY — for a video ad use clone_video with its link, then render_ad. Bills as one image generation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "imageUrl": "<imageUrl>"
    },
    "name": "clone_static"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoa profile id/name from list_brands to clone for; omit to use the active profile
get_costNotrue: return the price only; nothing runs or bills
imageUrlYesthe URL of the static ad image to clone. Using a real person’s face, likeness or voice confirms you are them or have their consent, take full, unlimited responsibility for its use and will cover any claim against Hermoso (hermoso.ai/terms). Paid plan only; recorded.
idempotency_keyNochosen once, resent unchanged on retries: the same key never buys twice
expected_creditsNothe get_cost price; refused unbilled if the live price differs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.532
    • addedInput schema / properties / expected_credits
      Added value: +{
      +  "description": "the get_cost price; refused unbilled if the live price differs",
      +  "type": "number"
      +}
    • addedInput schema / properties / get_cost
      Added value: +{
      +  "description": "true: return the price only; nothing runs or bills",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "chosen once, resent unchanged on retries: the same key never buys twice",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brandId / description
      Previous value: -"a brand id/name from list_brands to clone for; omit to use the active brand"New value: +"a profile id/name from list_brands to clone for; omit to use the active profile"
  3. Changed1 schema field changedv0.1.366
    • changedInput schema / properties / imageUrl / description
      Previous value: -"the URL of the static ad image to clone; a real person in it confirms their likeness consent"New value: +"the URL of the static ad image to clone. Using a real person’s face, likeness or voice confirms you are them or have their consent, take full, unlimited responsibility for its use and will cover any claim against Hermoso (hermoso.ai/terms). Paid plan only; recorded."
  4. Changed1 schema field changedv0.1.285
    • changedInput schema / properties / imageUrl / description
      Previous value: -"the URL of the static ad image to clone"New value: +"the URL of the static ad image to clone; a real person in it confirms their likeness consent"
  5. Addedv0.1.227

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, but the description adds the cost model ('Bills as one image generation') and the transformation contract (source branding fully removed, user's assets substituted), which are not derivable from annotations. It stops short of describing failure modes or how the result is returned, which keeps it below a 5.

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 trigger, the transformation, the parameter hint, the sibling exclusion and the billing note are packed into a few front-loaded sentences with little filler. The 'Pass imageUrl = the static ad image to clone' sentence is somewhat redundant with the schema, a minor waste.

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 billing, open-world generation tool with no output schema, the description covers what it does, what it costs, what it preserves and what it strips. It leaves unstated how the result is delivered and whether policy checks precede generation, which are the remaining gaps for a tool of this complexity.

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 description coverage is 100%, so every parameter is already documented in the schema, including the idempotency key, get_cost and expected_credits semantics. The description only restates that imageUrl is the ad to clone and adds the 'brandId picks another profile, like use_brand' analogy, so it contributes marginally beyond the schema baseline.

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 gives a concrete verb and resource ('rebuilds it on-brand' a static/image ad) and spells out the transformation: same layout, composition and energy but the user's product, colours, logo and voice with source branding removed. It explicitly contrasts with clone_video ('IMAGES ONLY'), so an agent can separate it from its nearest sibling without opening the 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?

It opens with an explicit trigger ('Use this when the user wants their own version of a static ad they like, a competitor's or any reference') and gives an explicit exclusion plus the alternative route ('for a video ad use clone_video with its link, then render_ad'). It also notes brandId behaves like use_brand, routing the agent correctly on brand selection.

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