Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Export video for delivery

video_export
Destructive

Re-encode an existing video for publishing-ready delivery with a quality preset and output format; the source stays read-only and a new output file is created.

Instructions

Re-encode an existing video for final delivery using a quality preset and output format. Use this for publishing-ready renders; use video_convert when the main goal is container/codec conversion. The source video is read only and a new output file is produced.

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format for delivery. Supported values are mp4, webm, gif, and mov.mp4
qualityNoDelivery quality preset: low, medium, high, or ultra.high
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYesAbsolute path to an existing local video file. The input file is read only.
output_pathNoDestination video path. Auto-generated when omitted; an existing supplied path may be overwritten.
c2pa_manifest_pathNoOptional C2PA manifest definition JSON to sign the final mp4 export.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.4
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / c2pa_manifest_path
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional C2PA manifest definition JSON to sign the final mp4 export.",
+  "title": "C2Pa Manifest Path"
+}
  3. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / format / description
      Added value: +"Output format for delivery. Supported values are mp4, webm, gif, and mov."
    • 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 / quality / description
      Added value: +"Delivery quality preset: low, medium, high, or ultra."
  4. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds the important clarification that 'the source video is read only and a new output file is produced,' which scopes the destructive risk to the destination. It does not discuss overwrite semantics or that re-encoding is slow/lossy, which would have made it fully self-sufficient for a write tool.

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?

Three short sentences, front-loaded with the action and the differentiator, then the exclusion, then the read-only/mutation scope. Every sentence earns its place with no filler.

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?

With annotations and a full-coverage schema plus an output schema, the description covers purpose, alternative routing, and source-safety. Minor gaps: it doesn't clarify the overwrite/protection interaction or the C2PA signing side effect, but those are documented in the schema itself.

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 coverage is 100%, so format, quality, overwrite, output_path and c2pa_manifest_path are all documented in the schema. The description only echoes 'quality preset and output format' without adding syntax, defaults, or tradeoff guidance (e.g. which quality preset suits which delivery target), so it meets but does not exceed the baseline.

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 and resource ('Re-encode an existing video for final delivery') plus the distinguishing mechanism (quality preset, output format). It explicitly contrasts with video_convert, so an agent can distinguish it from the closest sibling 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?

Gives an explicit when-to-use ('publishing-ready renders') and a named alternative with the condition that selects it ('use video_convert when the main goal is container/codec conversion'). Nothing is left to inference about routing.

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