Skip to main content
Glama

Extract Audio

extract_audio
Destructive

Extract audio from a media file into MP3, AAC, WAV, or a copied-codec file, returning the output path. Use it to isolate sound from screencasts for transcription or editing.

Instructions

Extract the audio track of a media file to its own file (mp3, aac, wav, or copy). Returns the output path.

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": {
      "input": "<input>",
      "format": "<format>"
    },
    "name": "extract_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the source media.
formatYesAudio output codec. copy keeps the source codec without re-encoding.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
overwriteNoAllow replacing an existing file at the output path (default false).

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.47.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the write/overwrite risk is flagged by structured data. The description adds that output goes 'to its own file' and returns that path, but does not restate the overwrite default or warn that an existing file at the target path may be replaced — context that would matter for a destructive tool.

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?

A single front-loaded sentence with no filler; the operation and formats come first. The trailing 'Returns the output path' is largely redundant given the tool has an output schema, costing it a perfect score.

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-coverage schema, annotations covering the safety profile, and an output schema handling return values, the description is sufficient to call the tool correctly. The remaining gap is sibling disambiguation against convert and the audio-processing tools, which the description does not address.

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%, with input, format (including the 'copy' semantics), output, and overwrite default all documented inline, so the baseline is 3. The description only repeats the format enum already listed in the schema and adds no new meaning.

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 ('Extract') and resource ('audio track of a media file'), enumerates the supported output formats, and produces a distinct artifact ('its own file'), which separates it from siblings like convert, normalize_audio, and denoise. An agent can identify the operation 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 Guidelines3/5

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

Usage is implied by the operation itself (pull the audio track out of a media file), but the description never says when to pick this over convert, which could plausibly also produce an audio file, or over normalize_audio/denoise for audio-only post-processing. No exclusions or prerequisites are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.