Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Import audio

import_audio

Imports one or more audio files into the project at the given position and saves it. Note: importing creates a new track holding the files.

Instructions

Imports one or more audio files into the project at the given position and saves it. Note: importing creates a new track holding the files.

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>",
      "files": "<files>"
    },
    "name": "import_audio"
  }
}

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
filesYesAudio file paths to import
projectYesPath to the .audium project package (absolute paths recommended)
position_secondsNoTimeline position for the files (default 0)

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

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the project is saved and that a new track is created, which are important side effects beyond the schema. However, it omits permissions, supported file formats, conflict/duplicate behavior, and error conditions, leaving meaningful gaps for a mutation tool.

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?

Two tightly written sentences, front-loaded with the core action and followed by an important side-effect note. There is no filler or redundancy.

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?

The description covers the core action and the key structural side effect (new track, save), and the input schema is fully described. But for a mutation tool with no annotations and no output schema, an agent would still lack guidance on return values, failure modes, and file-format constraints.

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 all four parameters are already documented with descriptions. The description adds only a light mapping ("one or more audio files" to the files array, "at the given position" to position_seconds) and no extra syntax or format detail. Baseline 3 is appropriate.

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 (imports), resource (audio files), target (project), and location (given position), plus the side effect of saving. The note that importing creates a new track helps distinguish it from clip-placement siblings like place_clip, though no sibling is named explicitly.

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 implies the tool is for bringing external audio files into a project, but it gives no explicit when-to-use guidance, no preconditions, and no alternatives. It does not say when to use import_audio versus assemble, place_clip, or create_project.

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