Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_write_metadata

Write metadata tags such as title and artist to video or audio files, saving to a specified output path or auto-generated file.

Instructions

Write metadata tags to a video/audio file.

Args: input_path: Absolute path to the input file. metadata: Dict of tag key-value pairs (e.g. {'title': 'My Video', 'artist': 'Me'}). output_path: Where to save the output. Auto-generated if omitted.

Input Schema

NameRequiredDescriptionDefault
metadataYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
output_pathNo

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

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It mentions that output_path is auto-generated if omitted, but does not explain overwrite behavior, whether the input file is modified, file safety constraints, permissions, or other mutation side effects.

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 short, front-loaded with the core action, and organized as a useful args list. Every line adds practical meaning without unnecessary repetition.

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?

The presence of an output schema reduces the need to explain return values, and the parameter descriptions cover most invocation details. However, for a mutation tool with no annotations, the description should more fully address overwrite semantics and file-safety behavior to be complete.

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 description coverage is low at 25%, so the description compensates well for three of four parameters: input_path is described as an absolute path, metadata is explained with an example, and output_path is described as optional with auto-generation. It does not mention the overwrite parameter, but the schema itself already documents that field.

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 verb and resource: writing metadata tags to a video/audio file. It is understandable independently of siblings, but it does not explicitly differentiate itself from video_read_metadata or clarify the write/read relationship.

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?

The description states what the tool does but gives no explicit when-to-use guidance, no prerequisites, and no alternatives such as video_read_metadata for reading existing tags. Usage is only implied by the verb 'Write'.

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