Skip to main content
Glama
Hermoso

Hermoso

Official

Product sizzle

product_sizzle

Render a faceless 18–30s product sizzle ad from a packshot: dice one 15s hero clip into fast cuts with typeset spec/CTA cards; confirm credit cost before calling.

Instructions

Render an 18-30s PRODUCT SIZZLE: ONE 15s Seedance 2.5 hero clip of the product, diced into fast cuts and intercut with typeset spec/CTA cards on a brand-coloured grain background. No music unless asked (music / musicMood); its own sound carries the cut. Faceless by design — no people, no voiceover, no spoken lines; the cards carry every word, so nothing is left to a video model's spelling. Pass a real packshot as refImage or the label will not be yours. EXPENSIVE — the hero clip is the only paid leg and it is a full 15s Seedance 2.5 render: ≈870 credits at the DEFAULT 1080p, ≈360 at 720p, ≈170 at 480p; a 4k ask renders on Seedance 2.0, the only Seedance tier with 4k, ≈2,360 (call hermoso_capabilities for the live seedance-2.5 per-duration numbers; the dicing and the cards are free; an asked-for bed adds a few). Confirm the spend with the user before calling. For a talking/UGC ad use render_ad or generate_avatar; for a cheap deterministic format use make_template_ad.

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

Input Schema

NameRequiredDescriptionDefault
ctaNoclosing CTA line, ≤30 chars
musicNotrue only when the user asked for music
specsNoup to 4 spec lines for the typeset cards, ≤26 chars each
styleNothe LOOK of the sizzle (same price for every look): hypermotion (Fast cuts, crash zooms and speed ramps), product_2d (The real product with playful hand-drawn 2D animation around it), typography (Product framed by huge bold letterforms in the brand colours), dark_minimal (Moody, premium, a single hard light on black), color_pop (Bright saturated colour, glossy, joyful), mixed_media (Editorial collage: paper, cut-outs and texture around the product), saas (For apps and software: floating screens, light trails, particles), product_showcase (Hero commercial: ingredients, splashes and a clean pack shot). Default hypermotion.
promptYeswhat the sizzle should show — the product, the setting, the look
secondsNofinished length, clamped to 18-30s (default 25). The PAID hero render is always 15s regardless — this only changes how the cuts and cards are packed
get_costNotrue: return the price only; nothing runs or bills
refImageNoproduct packshot URL that anchors the real label — strongly recommended
brandNameNobrand name on the cards — defaults to the workspace brand
musicMoodNobed mood (driving / cinematic / upbeat), only when music was asked for
resolutionNohero-clip resolution and therefore the whole cost — DEFAULT '1080p' (≈1,040 credits); '720p' ≈470, '480p' ≈220, '4k' ≈4,130
aspectRatioNo'9:16' default; anything the Seedance row that renders it does not list falls back to 9:16
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. Changed5 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"
      +}
    • addedInput schema / properties / music
      Added value: +{
      +  "description": "true only when the user asked for music",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / musicMood / description
      Previous value: -"music-bed mood, e.g. driving / cinematic / upbeat"New value: +"bed mood (driving / cinematic / upbeat), only when music was asked for"
  2. Changed1 schema field changedv0.1.519
    • changedInput schema / properties / aspectRatio / description
      Previous value: -"'9:16' default; anything the seedance-2 catalog entry does not list falls back to 9:16"New value: +"'9:16' default; anything the Seedance row that renders it does not list falls back to 9:16"
  3. Changed1 schema field changedv0.1.454
    • addedInput schema / properties / style
      Added value: +{
      +  "description": "the LOOK of the sizzle (same price for every look): hypermotion (Fast cuts, crash zooms and speed ramps), product_2d (The real product with playful hand-drawn 2D animation around it), typography (Product framed by huge bold letterforms in the brand colours), dark_minimal (Moody, premium, a single hard light on black), color_pop (Bright saturated colour, glossy, joyful), mixed_media (Editorial collage: paper, cut-outs and texture around the product), saas (For apps and software: floating screens, light trails, particles), product_showcase (Hero commercial: ingredients, splashes and a clean pack shot). Default hypermotion.",
      +  "enum": [
      +    "hypermotion",
      +    "product_2d",
      +    "typography",
      +    "dark_minimal",
      +    "color_pop",
      +    "mixed_media",
      +    "saas",
      +    "product_showcase"
      +  ],
      +  "type": "string"
      +}
  4. Addedv0.1.161

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only tell us it is a non-read-only open-world call; the description goes far beyond, disclosing that the hero render is the sole paid leg, the approximate credit cost per resolution tier, that dicing and cards are free, that a 4k ask silently switches to Seedance 2.0, and which call gives live pricing. It also exposes protective mechanisms (idempotency_key never buys twice, expected_credits refuses unbilled on price drift) that the annotations do not convey.

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 what gets produced, then constraints, then cost, then alternatives — the ordering matches how an agent needs it. It is dense and heavily parenthetical, and the long EXPENSIVE sentence restates pricing already in the schema (with different figures), which is waste that actively misleads.

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 14-parameter, non-idempotent, expensive render this covers format, constraints, cost, alternatives, and two safety params, which is a lot of what an agent needs. The remaining gap is output: with no output schema and no mention of what comes back (asset URL, job id, whether polling is needed), an agent cannot tell how to retrieve the result — notable for a tool this costly.

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 coverage is 100%, so the baseline is 3 and the description adds little that the schema does not already say — it mostly repeats 'no music unless asked' and the refImage recommendation already in the schema. Worse, its pricing conflicts with the schema: the description says ≈870 at 1080p and ≈2,360 at 4k, while the schema says ≈1,040 and ≈4,130, so an agent quoting a price gets two different numbers. The conflicting duplication cancels any credit above 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?

Names a specific verb+resource ('Render an 18-30s PRODUCT SIZZLE'), then defines the artifact precisely: one 15s hero clip diced into fast cuts intercut with typeset spec/CTA cards on grain. It explicitly distinguishes itself from siblings ('For a talking/UGC ad use render_ad or generate_avatar; for a cheap deterministic format use make_template_ad'), so an agent can route without opening another 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?

States when to use it, names two concrete alternatives with the conditions that select them, and adds hard prerequisites: pass a real packshot as refImage, no music unless asked, and confirm spend with the user before calling. Exclusions ('faceless by design — no people, no voiceover') are stated up front.

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