Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_extract_audio

Extract the audio track from a video file and save it as MP3, AAC, WAV, OGG, or FLAC. Specify an input video and optional output path to separate audio for transcription, editing, or reuse.

Instructions

Extract the audio track from a video file.

Args: input_path: Absolute path to the input video. output_path: Where to save the audio file. Auto-generated if omitted. format: Audio format (mp3, aac, wav, ogg, flac).

Input Schema

NameRequiredDescriptionDefault
formatNomp3
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. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It mentions that output_path is auto-generated when omitted, which is useful, but says nothing about overwrite/conflict behavior, whether existing files are replaced, codec/quality implications of the chosen format, or whether the source video is left untouched.

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?

Compact docstring with the operation stated up front and per-argument notes below; every line adds information. The Args list is slightly formal for four parameters but not wasteful.

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 needn't be explained, and the three core parameters are covered. However, for a file-writing tool with no annotations, the omission of overwrite/conflict semantics and of distinctions from sibling audio tools leaves meaningful gaps.

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 only 25%, and notably the format parameter has no enum in the schema; the description compensates by listing the accepted values (mp3, aac, wav, ogg, flac), which is genuine added value. input_path and output_path semantics are also clarified (absolute path, auto-generation when omitted); only 'overwrite' is left to the schema's own description.

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?

"Extract the audio track from a video file" names a specific verb and resource, so the agent immediately knows the operation. It does not distinguish itself from near-neighbors such as video_normalize_audio, video_mix_audio, or video_add_audio, which an agent could plausibly confuse with it.

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 gives no when-to-use guidance, no prerequisites (e.g. input must be a video with an audio stream), and never names an alternative for related audio tasks. The agent must infer usage purely from the name.

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