Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Restyle a video

restyle_video

Redraw every frame of a video in a new visual style, keeping shots, motion, timing and sound. Use preset looks, your own words, or reference images.

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, the strongest look on a face); none -> wan (Wan 3.0 Prime, ≤15s) else seedance (Seedance 2.5, 4-30s). Paid; dryRun quotes it. One change only: edit_video.

Input Schema

TableJSON 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. 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"
+}
  2. Addedv0.1.372

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only give the generic readOnly/idempotent/destructive profile; the description adds the operation is Paid with dryRun quoting, the deterministic auto engine-selection rules with duration limits per engine, that faceRoute requires explicit user consent and paid plans, and that characters carries a recorded legal-liability declaration. This is meaningful behavioral context not derivable from structured fields.

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?

Dense and front-loaded: the core verb and preservation rule come first, then look options, then engine routing, then cost and the sibling. Heavy caps and slash-shorthand make it slightly cryptic, but nearly every clause carries actionable information.

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-parameter, no-output-schema mutation tool, it covers cost, consent gating, engine selection, and look inputs well. It does not say what the call returns (job handle vs. final video) or whether the operation is asynchronous, which would help an agent chain follow-up calls such as get_job.

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 baseline is 3, but the description adds real meaning: it disambiguates the three look-specifying paths (style, describe, styleImages), explains what auto resolves to and why, and encodes the consent precondition on faceRoute. It omits resolution defaults and how describe composes with a preset, so it falls short of a 5.

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+resource ('RESTYLE a clip into a new LOOK') and immediately bounds what is preserved (shots, motion, camera, framing, timing, sound) versus what changes (every frame redrawn). It also explicitly separates itself from the nearest sibling, edit_video, so an agent can route without opening either 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?

Explicit selection rules: three ways to specify a look (a preset id via hermoso_capabilities, own words via describe, or styleImages), engine auto-routing logic keyed to clip content, and the hard exclusion 'One change only: edit_video.' When-not-to-use is stated, not implied.

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