Skip to main content
Glama
Sign In
kinocut

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Edit operations (trim, merge, text, convert, export, metadata, batch)

video_edit_ops
Destructive

Run a named video editing operation with its parameters to trim, convert, overlay, or extract audio via the kinocut MCP server.

Instructions

Run one edit operation by name; params holds its arguments. Required arguments: list_operations; full schema: describe_operation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "video_edit_ops"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoThe operation's arguments.
operationYes
overwriteNoAllow replacing existing media files.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the description's only added behavior is that arguments live in 'params'. For a dispatcher spanning 44 operations it never mentions that these operations write media files, that the overwrite flag controls replacement, or that behavior varies widely per operation.

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?

Two short clauses, front-loaded with the core mechanism followed by the discovery path. Nothing is padded, though the phrase 'Required arguments: list_operations; full schema: describe_operation' reads like a terse note rather than clean prose.

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 and the discovery tools are pointed to, so basic callability is covered. Still, a 44-operation destructive dispatcher with a free-form params object warrants at least a note on overwrite semantics and on the range of operations the enum contains.

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 67% and the 'operation' enum lists 44 values with no per-value explanation. The description adds real value by routing the agent to describe_operation for the full schema and by explaining that 'params' is a free-form argument bag, but it says nothing about which operations need which keys.

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

Purpose3/5

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

The description does state the mechanism: 'Run one edit operation by name' with arguments in 'params', which is a specific verb and resource. But it never clarifies how this generic dispatcher relates to dedicated siblings such as video_trim, video_merge, or video_add_text, so an agent cannot tell whether those are shortcuts for the same underlying operations.

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?

It gives a workflow hint by naming the required discovery arguments, pointing to list_operations and describe_operation before calling. It offers no when-to-use or when-not-to-use guidance relative to the dedicated siblings, nor any precondition for choosing this entry point.

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