Hermoso

Official

Overview Schema Source Related Servers Discussions Admin

Edit a video clip

edit_video

Swap a product into a video or change one named element from a plain instruction while preserving motion, timing, framing, cuts, and lighting.

Instructions

SWAP AN OBJECT IN A VIDEO ('replace the cup with our can' + the product photo as elements) or 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

Name	Required	Description
`video`	Yes	the source video URL (a render, job result or list_library)
`engine`	No	default auto: Seedance 2.5 Edit without a real-looking person, else Kling O3 Edit
`literal`	No	true = send the instruction exactly as written, with no preserve/lock wrapper
`elements`	No	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
`lighting`	No	default auto: keep the source light unless the change needs new light (night, a lamp, fire). 'preserve' or 'relight' forces it
`faceRoute`	No	'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.
`keepAudio`	No	default true: keep the source audio; false = silent
`previewAt`	No	second to preview (default 0); resend with previewStill
`reference`	No	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
`instruction`	Yes	the change, in the user’s own words
`previewStill`	No	the still a previewFirstFrame call returned; the clip then matches the changed thing to it
`interactionId`	No	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.
`previewFirstFrame`	No	true = 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.

Changed2 schema fields changedv0.1.374Oct 5, 2026

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"
+}

Changed11 schema fields changedv0.1.320Sep 26, 2026

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)"

Changed1 schema field changedv0.1.252Sep 18, 2026

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"
+}

Addedv0.1.161Aug 27, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that motion/timing/framing/cut/lighting are preserved by a prompt wrapper, that previewFirstFrame quotes but does not run the paid clip, that the reply includes a free fidelity score and flags over-editing, and that faceRoute is a rights attestation requiring user say-so. These are cost and safety facts annotations cannot convey.

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 zero filler sentences, but the prose is extremely dense with nested parentheticals and quoted examples, making the preview-loop mechanics harder to parse than they need to be. Every sentence carries information; the structure could be cleaner.

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 13-parameter, no-output-schema, non-idempotent generation tool, the description covers purpose, preservation contract, cost gating via preview, model routing, rights attestation, and failure/feedback signals. An agent has everything needed to invoke it correctly and to avoid the paid call by mistake.

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 3 is the baseline, but the description adds real meaning: it explains the literal wrapper, the lighting override semantics, the previewStill/previewAt handoff, and that elements ground identity while reference anchors material. It restates a few schema-documented behaviors rather than adding new ones, keeping it below 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 pair (swap an object / edit an existing clip) with concrete example instructions, and explicitly distinguishes itself from post_edit, generate_video, render_ad, dub_video and recast_motion. An agent can identify the correct tool 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?

Gives explicit when-to-use examples ('change only the mug to red', 'make it nighttime'), explicit when-NOT-to-use cases mapped to named sibling tools, plus operational guidance: one change per call, best on 3-15s clips, and the previewFirstFrame two-step loop.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Edit a video clip

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools