Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Rotate or flip video

video_rotate
Destructive

Rotate a video by 90, 180, or 270 degrees and apply horizontal or vertical flips, then render a new output file while leaving the original unchanged.

Instructions

Rotate and/or flip an existing video and render a new output file. Supports right-angle rotations plus horizontal and vertical flips; the input video is not modified.

Input Schema

NameRequiredDescriptionDefault
angleNoClockwise rotation angle in degrees. Supported values are 0, 90, 180, and 270.
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.
flip_verticalNoMirror the video vertically after rotation when true.
flip_horizontalNoMirror the video horizontally after rotation when true.

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. Changed1 schema field changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed5 schema fields changedv1.5.1
    • addedInput schema / properties / angle / description
      Added value: +"Clockwise rotation angle in degrees. Supported values are 0, 90, 180, and 270."
    • addedInput schema / properties / flip_horizontal / description
      Added value: +"Mirror the video horizontally after rotation when true."
    • addedInput schema / properties / flip_vertical / description
      Added value: +"Mirror the video vertically after rotation when true."
    • 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."
  4. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description usefully adds that the *input* video is never modified and a new output file is written, which clarifies what the destruction hint actually applies to. It stops short of discussing overwrite/conflict handling, but the schema covers that.

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?

Two sentences, front-loaded with the action and result, with the immutability guarantee appended where it matters. No filler or redundant restatement of the title.

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 a full output schema and fully described parameters, the description only needs to convey intent and side effects, which it does. The one remaining gap is that it doesn't state the rotation-then-flip ordering implication for the caller beyond the schema's per-param notes.

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 every parameter (angle with its allowed values, both flip flags, output_path defaults, overwrite protection) is already documented in structured form. The description echoes the rotation/flip capability but adds no new syntax, ordering, or default semantics beyond the schema.

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 pair (rotate/flip) plus the resource (an existing video) and the outcome (a rendered new output file). This is unambiguously distinct from sibling transforms like video_crop, video_resize, and video_reverse, which change geometry or time order rather than reorienting the frame.

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

Usage Guidelines3/5

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

The description implies usage by constraining the operation to right-angle rotations and mirrors, and notes the input file is untouched. However, it gives no explicit when-to-use/when-not guidance and never names an alternative for cases like arbitrary-angle correction or cropping.

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