Skip to main content
Glama
ffmpeg-mcp

ffmpeg-mcp

by yambal

trim_audio

Trim an audio file to a specific time range by specifying start and end times or a duration, then save the extracted segment to a new file.

Instructions

Trim audio file to a specific time range

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_path": "<input_path>",
      "output_path": "<output_path>",
      "start_time": "<start_time>"
    },
    "name": "trim_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
durationNoDuration to extract (format: HH:MM:SS or seconds)
end_timeNoEnd time (format: HH:MM:SS or seconds). Used if duration is not specified
input_pathYesPath to the input audio file
start_timeYesStart time (format: HH:MM:SS or seconds, e.g., '00:01:30' or '90')
output_pathYesPath for the output trimmed audio file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails it: nothing says whether the source file is modified or preserved, whether output_path is overwritten if it exists, or what happens on invalid ranges. 'Trim' implies a file-writing mutation, but the side effects are undisclosed.

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. It is efficient, though the brevity is closer to under-specification than disciplined concision given what remains unstated.

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?

A five-parameter file-mutating tool with no annotations and no output schema needs at least a note on write semantics and failure modes. The intent is captured adequately, but the operational context an agent needs to invoke it safely is missing.

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%, so the baseline is 3; each parameter already documents its format and the duration-vs-end_time precedence. The description adds no extra meaning beyond what the schema states.

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 names a specific verb and resource ('Trim audio file') plus a scope qualifier ('to a specific time range'), so an agent can tell what it does. It does not differentiate from siblings like convert_audio or extract_audio, which the name alone leaves to inference.

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?

There is no guidance on when to use this versus alternatives such as extract_audio or convert_audio, and no stated prerequisites (e.g. that the input must exist or be decodable). The only conditional logic present lives in the schema, not the description.

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