Skip to main content
Glama
Hermoso

Hermoso

Official

Clone a video for your brand

clone_video

Remake a TikTok, Instagram Reel, Facebook, X, or direct video link into an on-brand ad storyboard by analyzing its hook, pacing, and cuts, then swapping in your product, cast, and message.

Instructions

Remake a video you like FOR THIS BRAND from its link — a TikTok, Instagram Reel, Facebook video or reel, X post, or a direct video file URL. YouTube does not let us download videos, so a YouTube link is refused up front and nothing is charged; the user downloads it themselves and uploads the file (upload_file). Hermoso WATCHES it first (frames across the whole clip plus a transcript of the voiceover, on-screen text and cut map), then plans a storyboard that keeps its hook device, structure, jump cuts and pacing while swapping in THIS brand's product, cast, setting and words — never the original's words, face or brand. The new ad MATCHES THE ORIGINAL'S LENGTH (capped at 120s) unless durationSeconds is given. Renders nothing: pass the returned creative to render_ad to make the video. Costs the plan plus about 2 credits to read the link. The reply says exactly what was watched, and when a platform will not hand over the footage (YouTube sometimes refuses servers) it says the plan rests on the captions and thumbnail only. For a local file, upload_file it first and pass the URL. For a ready short-form FORMAT instead of a link (a Reel / TikTok structure with its own captions and a Comment-keyword close), use make_short. Reuse a style: save_video_preset.

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

Input Schema

NameRequiredDescriptionDefault
urlYesthe video to clone — a TikTok / Instagram Reel / Facebook / X link, or a direct https video file URL (not YouTube, which cannot be downloaded); a URL, not a local file path; use upload_file for local files
brandNobrand name or profile object; OMIT to use the workspace's saved brand (see get_brand)
changesNowhat to change or keep from the original, in the user's words (e.g. "same hook but in a gym", "keep the jump cut, older creator")
productNowhat the new ad sells, plus any angle or offer; omit to use the saved brand's product
get_costNotrue: return the price only; nothing runs or bills
languageNolanguage for the new ad's script and copy — default English
durationSecondsNooverride the length in seconds; omit to match the original
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. Changed4 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"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"the video to clone — a TikTok / Instagram Reel / Facebook / X / YouTube link, or a direct https video file URL; a URL, not a local file path; use upload_file for local files"New value: +"the video to clone — a TikTok / Instagram Reel / Facebook / X link, or a direct https video file URL (not YouTube, which cannot be downloaded); a URL, not a local file path; use upload_file for local files"
  2. Changed1 schema field changedv0.1.525
    • changedInput schema / properties / url / description
      Previous value: -"the video to clone — a TikTok / Instagram Reel / Facebook / X / YouTube link, or a direct https video file URL"New value: +"the video to clone — a TikTok / Instagram Reel / Facebook / X / YouTube link, or a direct https video file URL; a URL, not a local file path; use upload_file for local files"
  3. Addedv0.1.225

TDQS

A4.4/5.0
Behavior4/5

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

Far beyond the annotations: it discloses the cost (plan plus about 2 credits to read the link), that nothing renders, that the reply reports exactly what was watched and degrades to captions/thumbnail when a platform withholds footage, and that the 120s cap applies. idempotentHint=false is consistent with the description, since the idempotency_key is an opt-in guard rather than default behavior — but the description never says what happens on a retry without the key, which is the one behavioral gap.

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 the core action and the YouTube exclusion early, and nearly every clause carries a distinct constraint (cost, cap, no render, fallback behavior). It is a dense single paragraph that could be split into usage and behavior blocks for faster scanning, but there is little genuine filler.

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 nine-parameter, credit-spending, open-world tool with no output schema, the description covers cost, side effects, the required downstream call to render_ad, degraded-input handling, and the reply contents. An agent has everything needed to call it correctly and to explain the outcome to a user.

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 all nine parameters are already documented, and the description largely restates them (durationSeconds override, get_cost, the returned creative). It does add two facts not in the schema — the 120s length cap and that the URL must not be YouTube — but the remaining parameters get no extra meaning beyond the schema text.

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?

"Remake a video you like FOR THIS BRAND from its link" states a specific verb, resource and scoping constraint, and enumerates the accepted source types. It explicitly separates itself from render_ad (which makes the video), upload_file (local files), make_short (format-based) and save_video_preset, 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?

Gives explicit when-to-use and when-not-to-use rules: YouTube links are refused up front and nothing is charged, local files must go through upload_file first, and a ready-made short-form structure should use make_short instead. It also names save_video_preset for style reuse and render_ad as the mandatory next step.

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