Skip to main content
Glama
hermoso-ai

Hermoso

Official

Restyle a video

restyle_video

Redraw every frame of a video into a new look while keeping shots, motion, camera, timing, and sound. Apply preset, custom, or image-based styles for video ads.

Instructions

RESTYLE a clip into a new LOOK: every frame redrawn, shots, motion, camera, framing, timing and sound kept. Looks: Restyle looks in hermoso_capabilities (claymation, knitted yarn, cel-shaded CG anime…), your own words, or a look BUILT FROM YOUR IMAGES (styleImages); characters draws your own characters in. engine auto (default) picks by what is in the clip: a real-looking person -> kling (Kling O3 Edit, 3-15s); none -> wan (Wan 3.0, recommended, ≤15s) else seedance (Seedance 2.5, 4-30s); wan-prime = Wan 3.0 Prime by name (costs more). Paid; dryRun quotes it. One change only: edit_video.

Input Schema

NameRequiredDescriptionDefault
styleNoa look id from hermoso_capabilities (e.g. claymation, knitted-yarn, cel-shaded-anime-cg)
videoYesthe source video URL (a render, job result or list_library)
engineNodefault auto
describeNoa look in the user’s own words, when no preset fits, or extra detail on top of a preset
faceRouteNo'face_lane' = the user's "I own the rights to this face" for a real person in the source clip (paid plans). Only on the user's say-so, never on your own.
charactersNocharacters to draw the people as. 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.
resolutionNoSeedance and Wan; default 1080p
styleImagesNopictures that ARE the look (their style, never their subject)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.435
    • changedInput schema / properties / engine / enum
      Previous value: -[
      -  "auto",
      -  "seedance",
      -  "wan",
      -  "kling"
      -]New value: +[
      +  "auto",
      +  "seedance",
      +  "wan",
      +  "wan-prime",
      +  "kling"
      +]
  2. Changed6 schema fields changedv0.1.374
    • addedInput schema / properties / characters
      Added value: +{
      +  "description": "characters to draw the people as. 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.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 4,
      +  "type": "array"
      +}
    • addedInput schema / properties / engine
      Added value: +{
      +  "description": "default auto",
      +  "enum": [
      +    "auto",
      +    "seedance",
      +    "wan",
      +    "kling"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / faceRoute
      Added value: +{
      +  "description": "'face_lane' = the user's \"I own the rights to this face\" for a real person in the source clip (paid plans). Only on the user's say-so, never on your own.",
      +  "enum": [
      +    "face_lane"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / resolution
      Added value: +{
      +  "description": "Seedance and Wan; default 1080p",
      +  "enum": [
      +    "480p",
      +    "720p",
      +    "1080p"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / style / description
      Previous value: -"a look id from hermoso_capabilities (e.g. claymation, vhs-80s, film-noir)"New value: +"a look id from hermoso_capabilities (e.g. claymation, knitted-yarn, cel-shaded-anime-cg)"
    • addedInput schema / properties / styleImages
      Added value: +{
      +  "description": "pictures that ARE the look (their style, never their subject)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 9,
      +  "type": "array"
      +}
  3. Addedv0.1.372

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare non-readonly, non-idempotent, openWorld): it explains the engine auto-selection policy per source content, per-engine duration limits, cost differences for wan-prime, and consent/rights obligations for faceRoute and characters. This is rich behavioral disclosure an agent needs.

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 core purpose and the edit_video routing are front-loaded, and every clause carries information (looks, engine rules, cost, consent). It is dense and somewhat telegraphic with comma splices, but little is wasted.

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 an 8-param, no-output-schema tool it covers engine selection, cost, resolution constraints per engine, and consent requirements well. It does not explicitly state the async/job nature of the result, relying on sibling tools like get_job/list_jobs, which is a minor gap.

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 description coverage is already 100% (baseline 3), but the description adds semantics the schema lacks: how engine 'auto' resolves, that describe overlays/extend a preset, what styleImages represent (style, not subject), and the rights meaning of faceRoute. Adds genuine value on top of the schema.

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 (restyle) plus resource (clip/video) and defines the scope precisely: 'every frame redrawn, shots, motion, camera, framing, timing and sound kept.' It distinguishes itself from the sibling edit_video ('One change only: edit_video') so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear routing to the alternative edit_video, lists acceptable look sources (capabilities presets, free-form describe, styleImages), and states cost behavior ('Paid; dryRun quotes it'). It does not explicitly distinguish itself from recast_motion or clone_video, but the core when-to-use is well covered.

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