Skip to main content
Glama

mcp_opendaw_import_audio_to_tracks

Import an audio file into the DAW, optionally splitting it into stems on separate tracks for mixing and mastering. Choose from multiple stem separation modes or import as a single track.

Instructions

Import an audio file into the DAW, optionally split into stems on separate tracks.

One-call pipeline: audio file → (optional stem separation) → create instrument tracks → load each stem → place on tracks at start_beat. This is the Suno-to-DAW bridge: generate a track with Suno, download it, then import with stem splitting for mixing and mastering.

Without mode: loads the whole file as one track (simple import). With mode: splits into stems, creates one track per stem, loads and places each.

file_path: Absolute path to WAV/MP3/FLAC/OGG file on disk. mode: Stem separation mode (empty = no split, single track). Modes: "bs6" (6-stem), "scnet" (4-stem), "ensemble" (max quality), "polarformer" (vocal/instrumental), "drumsep" (drum parts). start_beat: Beat position to place the audio region(s) (default 0). bpm: Tempo for the project (affects beat alignment, default 120).

Returns: track count, per-track info (name, sample_id, duration, stem name), and suggested next steps (apply_genre_mix, render_full).

Examples:

Simple import — one track, no splitting

import_audio_to_tracks("/tmp/suno_track.wav")

Split into 6 stems, each on its own track

import_audio_to_tracks("/tmp/suno_track.wav", mode="bs6")

Vocal/instrumental split at beat 4

import_audio_to_tracks("/tmp/vocal.wav", mode="polarformer", start_beat=4)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
modeNo
file_pathYes
start_beatNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description fully discloses behaviors: it creates instrument tracks, loads stems, and describes the pipeline. It mentions side effects like track creation and returns detailed info.

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?

The description is well-structured with overview, parameter details, return info, and examples. It is slightly verbose but each section adds value. Could be tightened without loss of clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and presence of an output schema, the description covers all necessary aspects: return values (track count, per-track info, suggested next steps) and integration with other tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter (file_path, mode, start_beat, bpm) with details, default values, and mode options. Examples further clarify usage.

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?

The description clearly states it imports audio files, optionally splits into stems, creates tracks, and places them at start_beat. It uniquely positions itself as a 'Suno-to-DAW bridge', distinguishing it from other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides clear guidance on when to use (import audio, optionally with stem separation) and includes examples for different modes. However, it does not explicitly mention when not to use or provide alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AMEOBIUS-team/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server