Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Clone a static ad (old name)

remix_static

Clone a static ad image from a URL into your chosen brand profile. Legacy alias for clone_static; use clone_static for new calls.

Instructions

The OLD NAME of clone_static, kept so agents that already call it keep working. It is the same tool with the same inputs, result and cost; prefer clone_static.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandIdNoa profile id/name from list_brands to clone for; omit to use the active profile
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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."
  3. 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"
  4. Changed2 schema fields changedv0.1.227
    • changedInput schema / properties / brandId / description
      Previous value: -"a brand id/name from list_brands to remix for; omit to use the active brand"New value: +"a brand id/name from list_brands to clone for; omit to use the active brand"
    • changedInput schema / properties / imageUrl / description
      Previous value: -"the URL of the static ad image to remix"New value: +"the URL of the static ad image to clone"
  5. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "image": {
-      "description": "the served absolute URL of the remixed ad image",
-      "type": "string"
-    },
-    "model": {
-      "description": "the model label that rendered it",
-      "type": "string"
-    },
-    "residual": {
-      "description": "source-branding sweep result ({clean, note})"
-    },
-    "slots": {
-      "description": "the filled slot map (layout elements swapped to your brand)"
-    }
-  },
-  "type": "object"
-}New value: +null
  6. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description usefully adds that behavior and cost are identical to clone_static, but it does not describe the actual operation's side effects (it clones an ad image, paid plan, recorded) beyond what the schema text already carries.

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 tight sentences, zero filler. The identity and the routing recommendation are both front-loaded, which is exactly right for a deprecation shim.

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 deprecated alias with a complete schema and no output schema, this covers everything an agent needs: what it is, that it is equivalent to clone_static, and that clone_static should be preferred.

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 brandId and imageUrl are fully documented in the schema, including the paid-plan/consent note. The description only asserts inputs are the same as clone_static, adding no new parameter meaning — baseline 3 is appropriate.

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 states a specific identity: this is the OLD NAME of clone_static, same tool, same inputs, result and cost. It distinguishes itself from the sibling clone_static by name and explains the only reason it still exists (backward compatibility).

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 an explicit routing rule — 'prefer clone_static' — and names the exact condition under which remix_static is still the right call: agents that already call it. No inference required.

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