Skip to main content
Glama

extract_audio

Extracts a video's sound track and saves it as an .m4a file, making audio available for editing, transcription, or sharing.

Instructions

Saves the video's sound as an .m4a file.

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

Input Schema

NameRequiredDescriptionDefault
videoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds the useful fact that the artifact is an .m4a file, but says nothing about where the file is written, how it is named, or whether it overwrites existing output.

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?

One short sentence with zero filler, front-loading the action and naming the output format. Nothing could be removed without losing information.

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?

For a simple one-parameter tool with annotations covering the safety profile, the description is nearly sufficient. The remaining gap is what the call returns or where the .m4a lands, and with no output schema that information has no other home.

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 0% and the single `video` parameter is undocumented, so the description must compensate. It clarifies that `video` is the source whose sound is extracted, but does not say whether it is a file path, ID, or URL, which is the key ambiguity for a 1-parameter tool.

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?

Names a concrete verb and resource ("Saves the video's sound") plus the output format (.m4a), which clearly distinguishes it from siblings like remove_audio. It stops short of explicitly naming any sibling, so differentiation is implied rather than stated.

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 only implied by the wording: an agent can infer this extracts audio when the sound is wanted. There is no statement of when to prefer this over related operations (e.g., remove_audio) or any prerequisites.

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