Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Edit a video clip

edit_video

Change only a named thing in an existing clip from plain words—motion, timing, framing, and cut stay; lighting is kept unless the change needs new light.

Instructions

EDIT an existing clip from a plain instruction (video-to-video): the motion, timing, framing and cut stay, the named thing changes. 'change only the mug to red', 'make it nighttime', 'restyle it as claymation'. Your words are wrapped so the model keeps everything else identical, changes only what you named and repeats that lock; lighting is kept unless the change needs new light (set lighting to force either); literal:true sends your words as written. One change per call holds best. previewFirstFrame:true edits ONE still first (one image edit; previewAt picks the second) and quotes the clip; nothing else runs until you call again, ideally with previewStill. The reply scores how well the shot held outside the change (free) and flags an edit that touched more than asked. NOT for cuts/trims/end cards (post_edit), a new video (generate_video / render_ad), translation (dub_video) or a saved creator's face (recast_motion). Best on 3-15s clips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoYesthe source video URL (a render, job result or list_library)
engineNodefault auto: Seedance 2.5 Edit without a real-looking person, else Kling O3 Edit
literalNotrue = send the instruction exactly as written, with no preserve/lock wrapper
elementsNoOPTIONAL identity/product grounding (≤4): a creator portrait or the real product photo, so the edit restores the REAL thing. Describe each one in the instruction
lightingNodefault auto: keep the source light unless the change needs new light (night, a lamp, fire). 'preserve' or 'relight' forces it
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.
keepAudioNodefault true: keep the source audio; false = silent
previewAtNosecond to preview (default 0); resend with previewStill
referenceNoOPTIONAL image URL that anchors the MATERIAL of what changes (a fabric, a finish, a colour swatch, the real product). Only its surface is used, never its framing or light
instructionYesthe change, in the user’s own words
previewStillNothe still a previewFirstFrame call returned; the clip then matches the changed thing to it
interactionIdNoOPTIONAL: the interactionId an earlier Gemini Omni render or edit returned; the edit continues that clip on the same Omni model. If it cannot run, the video editor edits it and the reply says so.
previewFirstFrameNotrue = edit ONE still of the first frame first and quote the clip; the paid clip does not run

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.374
    • addedInput schema / properties / engine
      Added value: +{
+  "description": "default auto: Seedance 2.5 Edit without a real-looking person, else Kling O3 Edit",
+  "enum": [
+    "auto",
+    "seedance",
+    "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"
+}
  2. Changed11 schema fields changedv0.1.320
    • changedInput schema / properties / elements / description
      Previous value: -"OPTIONAL identity/product grounding (≤4): a creator portrait or the real product photo, so the edit restores the REAL thing instead of re-inventing it. Describe each one in the instruction. Leave out for a plain restyle"New value: +"OPTIONAL identity/product grounding (≤4): a creator portrait or the real product photo, so the edit restores the REAL thing. Describe each one in the instruction"
    • changedInput schema / properties / instruction / description
      Previous value: -"the exact transformation to apply, in the user’s own words"New value: +"the change, in the user’s own words"
    • changedInput schema / properties / interactionId / description
      Previous value: -"OPTIONAL: the interactionId an earlier Gemini Omni render or edit returned. The edit then continues that clip on the SAME Omni model from its own stored context (identity-true, no re-upload, usually cheaper). If that edit cannot run, the clip is edited by the video editor instead and the reply says so."New value: +"OPTIONAL: the interactionId an earlier Gemini Omni render or edit returned; the edit continues that clip on the same Omni model. If it cannot run, the video editor edits it and the reply says so."
    • changedInput schema / properties / keepAudio / description
      Previous value: -"default true — keep the source clip’s audio track. Set false to return the edit silent"New value: +"default true: keep the source audio; false = silent"
    • addedInput schema / properties / lighting
      Added value: +{
+  "description": "default auto: keep the source light unless the change needs new light (night, a lamp, fire). 'preserve' or 'relight' forces it",
+  "enum": [
+    "auto",
+    "preserve",
+    "relight"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / literal
      Added value: +{
+  "description": "true = send the instruction exactly as written, with no preserve/lock wrapper",
+  "type": "boolean"
+}
    • addedInput schema / properties / previewAt
      Added value: +{
+  "description": "second to preview (default 0); resend with previewStill",
+  "type": "number"
+}
    • addedInput schema / properties / previewFirstFrame
      Added value: +{
+  "description": "true = edit ONE still of the first frame first and quote the clip; the paid clip does not run",
+  "type": "boolean"
+}
    • addedInput schema / properties / previewStill
      Added value: +{
+  "description": "the still a previewFirstFrame call returned; the clip then matches the changed thing to it",
+  "type": "string"
+}
    • addedInput schema / properties / reference
      Added value: +{
+  "description": "OPTIONAL image URL that anchors the MATERIAL of what changes (a fabric, a finish, a colour swatch, the real product). Only its surface is used, never its framing or light",
+  "type": "string"
+}
    • changedInput schema / properties / video / description
      Previous value: -"the source video URL (from a previous render, a job result, or list_library)"New value: +"the source video URL (a render, job result or list_library)"
  3. Changed1 schema field changedv0.1.252
    • addedInput schema / properties / interactionId
      Added value: +{
+  "description": "OPTIONAL: the interactionId an earlier Gemini Omni render or edit returned. The edit then continues that clip on the SAME Omni model from its own stored context (identity-true, no re-upload, usually cheaper). If that edit cannot run, the clip is edited by the video editor instead and the reply says so.",
+  "type": "string"
+}
  4. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the standard readOnly/openWorld/idempotent/destructive hints: it discloses the preserve-and-lock wrapping behavior, that the quality score is free, that a previewFirstFrame call does not run the paid clip (implying normal runs are paid), and that the reply flags over-reaching edits. This is exactly the cost/behavior context annotations cannot express.

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 purpose and examples before the workflow and exclusion details, and every sentence carries usable information for a 13-parameter tool. It is dense to the point of run-on in the previewFirstFrame/previewAt sentence, which costs a point.

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?

Given 13 params, no output schema, and 3 enums, the description covers what an agent needs: model routing (engine), lighting semantics, the preview/approval loop, rights handling via faceRoute, and expected reply content (quality score plus over-edit flag). Parameter-level detail is safely delegated to a fully documented schema.

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 the baseline is 3. The description still adds value beyond the schema by explaining the interaction between previewFirstFrame, previewAt and previewStill ('previewAt picks the second'), and by giving concrete instruction phrasing for the required instruction param. Minor gain, but real.

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?

Opens with a specific verb+resource+mechanism ('EDIT an existing clip from a plain instruction (video-to-video)') and immediately constrains scope: motion/timing/framing/cut stay, only the named thing changes. It names the exact siblings it is not for (post_edit, generate_video, render_ad, dub_video, recast_motion), so an agent can disambiguate without opening any 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 when-not routing to five alternatives, plus positive-fit guidance ('Best on 3-15s clips', 'One change per call holds best'). The preview workflow is given a concrete when-to-use path (previewFirstFrame then call again, ideally with previewStill). Nothing about tool selection is left to inference.

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