Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Multiply an ad

multiply_ad

Turn one winning video ad into multiple variants by changing character, outfit, location, or objects while keeping the original cut, camera motion, pacing, and audio. Removes burned-in captions.

Instructions

MULTIPLY a winning video ad into N variants: each gets a NEW character, outfit, location and/or objects while the cut, the camera motion, the pacing and the ORIGINAL AUDIO stay exactly as they were (that is what made the ad work), and any burned-in captions are removed. Pass the source video URL (a previous render, a job result, list_library, or the top performer from post_performance / meta_insights). HOW: the source video itself DRIVES each variant (motion transfer from one image-edited opening frame), so every variant comes back the SAME LENGTH as the source with the same cut, the same performance and the original audio — only the person, outfit, set and props change. Sources up to 30 seconds work as they are; longer ones are refused for free with the way out (trim it first: post_edit with ops [{op:'trim', start:0, end:30}] — clip_video is the AI highlight clipper, not a trim). Returns the plan and ONE JOB PER VARIANT — call get_job on each until it reports done; do not describe a variant before its URL arrives. COST: quoteOnly:true returns the exact credits free: state that first. A paid planning read (planCredits) runs next, then each variant bills perVariantCredits. dryRun:true pays for that read; pass its plan back to render without paying again. Regions: pass regions:['Berlin','Tokyo'] to restyle variants per market; translation is a separate, explicit step — dub_video on a finished variant. change is what should change, in the user's own words ('older women', 'winter streets', 'swap the mug for our bottle'): every variant applies it and the variants still differ around it; a part of it about the voice, words, language, music, length or captions cannot change here, and the reply says so and names the tool that can.

Input Schema

NameRequiredDescriptionDefault
axesNowhat to vary: character, outfit, location, objects (default all four), or your own, e.g. "season"
planNothe `plan` a dryRun returned, rendered without planning again
countNohow many variants, 1-12 (default 6)
notesNoanything the variants must respect, e.g. "keep it women 25-40", "no gyms"
videoYesthe source video URL
changeNowhat should change, in the user's own words, e.g. 'older women, winter streets'; every variant applies it (omit to let the variants vary freely)
dryRunNotrue = the paid plan and the price, no render
regionsNomarkets to restyle for, one or more variants each, e.g. ["Berlin","Tokyo","São Paulo"] — visuals only; audio is never translated here
quoteOnlyNotrue = the exact credits, free; nothing runs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.489
    • changedInput schema / properties / dryRun / description
      Previous value: -"true = return the plan and the quote, render nothing"New value: +"true = the paid plan and the price, no render"
    • addedInput schema / properties / plan
      Added value: +{
+  "description": "the `plan` a dryRun returned, rendered without planning again"
+}
    • addedInput schema / properties / quoteOnly
      Added value: +{
+  "description": "true = the exact credits, free; nothing runs",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.1.366
    • addedInput schema / properties / change
      Added value: +{
+  "description": "what should change, in the user's own words, e.g. 'older women, winter streets'; every variant applies it (omit to let the variants vary freely)",
+  "type": "string"
+}
  3. Changed2 schema fields changedv0.1.285
    • changedInput schema / properties / axes / description
      Previous value: -"which axes to vary (default: all four)"New value: +"what to vary: character, outfit, location, objects (default all four), or your own, e.g. \"season\""
    • removedInput schema / properties / axes / items / enum
      Removed value: -[
-  "character",
-  "outfit",
-  "location",
-  "objects"
-]
  4. Addedv0.1.189

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: variants preserve source length, cut, camera motion, pacing, and original audio; burned-in captions are removed; one job is returned per variant; and get_job must be polled until done. It also explains the cost sequence around quoteOnly, dryRun, planCredits, and perVariantCredits, which is exactly the operational context an agent needs for a paid, non-idempotent render tool.

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 description is front-loaded with purpose and every sentence carries operational information, so it is not padded. However, the dense single-block prose and repeated cost/plan details make it harder to scan than a more structured presentation 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 complex creative render tool with nine parameters and no output schema, the description covers the missing pieces: job-based return flow, polling requirements, cost/planning behavior, length limits, regional behavior, and what the change parameter cannot do. Nothing essential appears to be missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description still adds meaningful semantics beyond the schema: quoteOnly is free and exact, dryRun pays for planning and its returned plan can be reused without paying again, regions affect visuals only, and change cannot alter voice, words, language, music, length, or captions. These are important distinctions not fully captured by the bare parameter descriptions.

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 verb and resource — multiply a winning video ad into N variants — and clearly defines what changes versus what remains fixed. It explicitly distinguishes itself from siblings like clip_video and dub_video, so an agent can identify its role 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 gives explicit when-to-use guidance, including valid video sources, the 30-second limit, and the fallback to post_edit for trimming while warning that clip_video is not a trim tool. It also states when to use dub_video for translation and how regions differ from translation, which covers alternatives and exclusions well.

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