kinocut

Overview Schema Source Related Servers Discussions Admin

Add video fade

video_fade

Destructive

Render fade-in and fade-out effects onto an existing video without altering the source file, using configurable durations and an optional output path.

Instructions

Render fade-in and/or fade-out effects onto an existing video without modifying the source file. Use fade_in for a fade from black at the start and fade_out for a fade to black at the end; output_path is created or overwritten.

Input Schema

Name	Required	Description
`crf`	No	Optional FFmpeg CRF override from 0 to 51, where lower means higher quality.
`preset`	No	Optional FFmpeg encoding preset: ultrafast, fast, medium, slow, or veryslow.
`fade_in`	No	Non-negative fade-in duration in seconds from black at the start.
`fade_out`	No	Non-negative fade-out duration in seconds to black at the end.
`overwrite`	No	Explicitly allow replacing existing media. Existing non-media files are protected.
`input_path`	Yes	Absolute path to an existing local video file. The input file is read only.
`output_path`	No	Destination video path. Auto-generated when omitted; an existing supplied path may be overwritten.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.16.4Oct 24, 2026

addedInput schema / properties / overwrite

Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}

Changed1 schema field changedv1.16.0Oct 3, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed6 schema fields changedv1.5.1Jun 4, 2026

addedInput schema / properties / crf

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional FFmpeg CRF override from 0 to 51, where lower means higher quality.",
+  "title": "Crf"
+}

addedInput schema / properties / fade_in / description

Added value: +"Non-negative fade-in duration in seconds from black at the start."

addedInput schema / properties / fade_out / description

Added value: +"Non-negative fade-out duration in seconds to black at the end."

addedInput schema / properties / input_path / description

Added value: +"Absolute path to an existing local video file. The input file is read only."

addedInput schema / properties / output_path / description

Added value: +"Destination video path. Auto-generated when omitted; an existing supplied path may be overwritten."

addedInput schema / properties / preset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional FFmpeg encoding preset: ultrafast, fast, medium, slow, or veryslow.",
+  "title": "Preset"
+}

First observedv0.2.0Mar 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds useful behavioral context: the source file is not modified and output_path is created or overwritten. It does not fully explain overwrite preconditions, but it meaningfully supplements the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tightly written sentences with no filler, and the core behavior and output behavior are front-loaded.

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?

Given the full schema coverage, output schema, and destructive annotations, the description is largely complete for correct invocation. The only minor gap is the absence of explicit guidance on when this tool should be used versus sibling effect tools.

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 description coverage is 100%, so the schema already documents all seven parameters, including crf, preset, overwrite, and path semantics. The description adds only marginal meaning by reiterating fade_in and fade_out behavior, which is already covered in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action and resource: rendering fade-in and/or fade-out effects onto an existing video. It distinguishes the specific fade semantics from other video effects, but it does not explicitly differentiate itself from sibling tools such as video_filter or transition tools.

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

Usage Guidelines2/5

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

It explains how to use the fade_in and fade_out parameters, but not when this tool should be chosen over alternatives or when it should be avoided. There is no explicit context for selecting video_fade versus other effect or transition tools.

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

Deploy Server