Skip to main content
Glama
Hermoso

Hermoso

Official

Save a creator

save_creator

Store a portrait and name as a reusable creator so the same person can appear in future ads; pass the saved image URL to avatar, video, or motion generation.

Instructions

Add a portrait to this workspace’s reusable CAST so the SAME person can star in future ads — the headless twin of the app’s + > Pick a creator > save. Pass the portrait’s public url (a generate_image render of an AI person, or a photo of a real person you have permission to use, or of yourself; never a photo just because it is public) plus a name to call them by; from then on list_creators returns them and their url can be re-passed to generate_avatar / generate_video / recast_motion. Saving is FREE and renders nothing (the one paid option is makeSheet, which makes their 16:9 character sheet). LIKENESS: leave source "generated" for an AI-made person (free on every plan) and use "upload"/"social" for a REAL person. 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.

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": {
      "name": "<name>"
    },
    "name": "save_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookNotheir canonical wardrobe/appearance in words — reused to hold the look steady across ads
nameYeswhat to call this creator (e.g. “Sarah”) — list_creators and the app’s picker match on it
brandNoprofile id/name from list_brands, this call only
imageNoREQUIRED except with useAnyway. public https url of the portrait (an existing render’s url, or any public photo). Not a local file path — upload it with upload_file first and save the url that returns
posesNoup to 4 extra full-body / angle plates of the SAME person (public urls) — they make a wider shot hold the identity
sheetNoa CHARACTER SHEET of this creator to keep (public url): one 16:9 image, full body on the left, a close portrait on the right. Free. Works on a creator already saved (pass just name + sheet)
voiceNoa default voice name for this persona (engines + voices are in hermoso_capabilities)
sourceNo"generated" (default) = an AI-made person; "upload" / "social" = a REAL person
makeSheetNoPAID (one image, see hermoso_capabilities job character_sheet): make that 16:9 character sheet FROM their saved portrait and keep it, so wide shots hold their full figure and outfit. Works on a creator already saved (pass just name + makeSheet). Describe their outfit head to toe in `look` first if it is not saved
useAnywayNoonly for a creator whose saved photo was flagged too unclear to cast (render_ad says so): true casts the current photo as it is, no new image needed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.532
    • addedInput schema / properties / makeSheet
      Added value: +{
      +  "description": "PAID (one image, see hermoso_capabilities job character_sheet): make that 16:9 character sheet FROM their saved portrait and keep it, so wide shots hold their full figure and outfit. Works on a creator already saved (pass just name + makeSheet). Describe their outfit head to toe in `look` first if it is not saved",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / sheet
      Added value: +{
      +  "description": "a CHARACTER SHEET of this creator to keep (public url): one 16:9 image, full body on the left, a close portrait on the right. Free. Works on a creator already saved (pass just name + sheet)",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"brand id/name from list_brands, this call only"New value: +"profile id/name from list_brands, this call only"
  3. Changed1 schema field changedv0.1.371
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "brand id/name from list_brands, this call only",
      +  "type": "string"
      +}
  4. Changed1 schema field changedv0.1.285
    • removedInput schema / properties / consented
      Removed value: -{
      -  "description": "REAL people only: the user has confirmed that person consented to their likeness being used in ads",
      -  "type": "boolean"
      -}
  5. Changed3 schema fields changedv0.1.272
    • changedInput schema / properties / image / description
      Previous value: -"public https url of the portrait (an existing render’s url, or any public photo). Not a local file path — upload it with upload_file first and save the url that returns"New value: +"REQUIRED except with useAnyway. public https url of the portrait (an existing render’s url, or any public photo). Not a local file path — upload it with upload_file first and save the url that returns"
    • addedInput schema / properties / useAnyway
      Added value: +{
      +  "description": "only for a creator whose saved photo was flagged too unclear to cast (render_ad says so): true casts the current photo as it is, no new image needed",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "image"
      -]New value: +[
      +  "name"
      +]
  6. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: saving is free and renders nothing, makeSheet is the sole paid path, the tool is paid-plan-only and recorded, and real-person likeness requires consent with a stated liability term. The openWorldHint/idempotentHint/destructiveHint flags are supplemented with concrete cost, plan, and legal consequences.

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?

Purpose and the free-vs-paid distinction are front-loaded, and no sentence is filler. However, it is delivered as one dense run-on paragraph with heavy capitalization and em-dashes, which makes the LIKENESS/consent block harder to scan than a short structured layout would be.

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 10-parameter mutation with no output schema, the description covers cost, plan gating, what persists, downstream consumers of the saved url, and the consent requirement. An agent has everything needed to decide whether to call it and what to expect afterwards.

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 baseline is 3; the description still adds cross-parameter meaning — image is required except with useAnyway, sheet/makeSheet operate on an already-saved creator with just name plus that flag, and source values carry plan and consent implications. It stops short of restating every parameter, which is appropriate given the schema already documents them.

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 and resource (add a portrait to the workspace's reusable CAST) plus the outcome (the same person can star in future ads), and anchors it to a concrete UI equivalent (+ > Pick a creator > save). It is clearly distinguishable from generate_avatar/generate_image, which produce renders rather than persist a persona.

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?

Explicitly says what to pass (portrait public url + name), what happens afterwards (list_creators returns them; the url can be re-passed to generate_avatar / generate_video / recast_motion), and names the alternative path for local files (upload_file first). It also flags the one paid option (makeSheet) against the otherwise free save, so an agent knows when cost is incurred.

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