Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Remove channel

remove_channel

Removes one channel (0-based) from a track, like deleting a channel strip in the GUI. Channel mappings and per-channel clip gains shift down; the audio files stay in the package.

Instructions

Removes one channel (0-based) from a track, like deleting a channel strip in the GUI. Channel mappings and per-channel clip gains shift down; the audio files stay in the package.

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": {
      "project": "<project>",
      "track": "<track>",
      "channel": "<channel>"
    },
    "name": "remove_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoName of the task this edit is part of, e.g. "remove speech pauses". In the open app, all edits with the same task name become one undo step: keep the name for every call of the task and change it when the next task starts. Without a task name, all edits of this session share one step
trackYesTrack id
channelYesChannel index within the track (0-based)
projectYesPath to the .audium project package (absolute paths recommended)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.7
    • addedInput schema / properties / task
      Added value: +{
      +  "description": "Name of the task this edit is part of, e.g. \"remove speech pauses\". In the open app, all edits with the same task name become one undo step: keep the name for every call of the task and change it when the next task starts. Without a task name, all edits of this session share one step",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral load and does it well: it discloses that channel mappings and per-channel clip gains shift down and that audio files remain in the package — key non-destructive, index-shifting semantics an agent could not infer. It omits return value and any failure conditions, which keeps it from a 5.

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 sentence, front-loaded with the verb and resource, with the consequences appended as a compact second clause. No filler.

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?

For an unannotated mutation tool this covers the important ground — what is destroyed, what shifts, what persists. The remaining gap is the post-call state (what the tool returns, e.g. updated channel count), which matters since there is no output schema.

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 100%, so all four parameters (including the task/undo-grouping semantics) are already documented in the schema. The description's '(0-based)' merely echoes the schema and it says nothing about the task or project parameters; baseline 3 applies.

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 the specific verb (removes) and resource (one channel from a track) with an index qualifier, and the GUI analogy ('deleting a channel strip') makes the operation unambiguous. Easily distinguished from siblings like remove_track or remove_clip.

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?

The GUI analogy implies when an agent would reach for it, but there is no explicit when-to-use guidance, no mention of the remove_track/remove_clip alternatives, and no note on edge cases such as removing the last channel on a track.

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