Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_cleanup

Delete intermediate video files after a workflow while preserving paths listed in keep. Use it to clean temporary outputs from multi-step pipelines without removing protected files.

Instructions

Delete intermediate video files after a workflow.

Useful for multi-step pipelines that leave temporary outputs. Files in keep are preserved even if listed in files.

Args: files: List of absolute paths to delete. keep: List of absolute paths to preserve (optional).

Input Schema

NameRequiredDescriptionDefault
keepNo
filesYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.

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. Addedv1.5.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important behavioral rule: the `keep` precedence over `files`. However, it says nothing about the irreversibility of deletion, what happens when a path is missing or is not media, or the `overwrite` safety valve — the tool is destructive and this is the main gap.

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?

The behavioral rule about `keep` is front-loaded in the first two sentences, which is exactly right. The Args block is somewhat redundant with the schema, though it earns its place by adding the "absolute paths" constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. For a destructive, annotation-free tool with a 33% schema coverage, the description should also cover frozen semantics — missing-file handling, non-media protection, and the role of `overwrite` — none of which are addressed beyond the `keep` rule.

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 only 33% (only `overwrite` has a schema description), so the description must compensate — and it does for two parameters, specifying that `files` and `keep` are absolute paths and documenting the precedence relationship between them. It entirely omits `overwrite`, which is the one parameter the schema already covers, so the practical gap is small.

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?

The description states a specific verb and resource ("Delete intermediate video files") and scopes it to post-workflow cleanup, which no sibling tool covers — the rest of the catalog transforms, renders, or inspects media rather than deleting scratch files. An agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines4/5

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

It gives a clear usage context ("after a workflow", "multi-step pipelines that leave temporary outputs"), which is enough to know when to call it. It stops short of naming alternatives or preconditions, such as whether this should run before or after export, or what to do if a pipeline step failed.

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