Skip to main content
Glama

project_export_audio

Export the entire Audacity project or current selection to an audio file at a specified path, with channel and format control via file extension.

Instructions

Export the project audio to a file. Format is determined by file extension.

MANDATORY: ALWAYS tell the user where the file will be saved BEFORE exporting. Example: "I'll save your audio to C:\Users\Name\Music\file.mp3"

NEVER save directly to the user's home folder (e.g. ~/file.mp3 or C:\Users\Name\file.mp3). ALWAYS save to a subfolder. If the user doesn't specify a path, call get_default_export_folder to get their Music folder and save there. Acceptable locations:

  • Music folder: ~/Music/file.mp3

  • Documents folder: ~/Documents/file.mp3

  • Desktop: ~/Desktop/file.mp3 NEVER save to the home folder root — this clutters the user's home directory.

Args: path: Absolute path for exported file. Extension determines format (wav, mp3, ogg, flac, aiff). num_channels: Number of channels (1=mono, 2=stereo). Default: 2 whole_project: Select every track and the whole timeline first. Default: True. Audacity's Export2 exports the CURRENT SELECTION, so leaving this on is what makes "export the project" mean the project. Set it to False only when you deliberately want the current selection.

The result carries a verified block read back from the written file: the container actually present, its sample rate, channels and duration. Audacity uses the sticky last-used exporter and will write AIFF into a path named .wav while reporting a WAV export, and it renders at the project sample rate rather than anything asked for here — so a warning appears when what landed on disk is not what was requested.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
num_channelsNo
whole_projectNo
Behavior5/5

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It details Audacity's sticky last-used exporter behavior, the fact that sample rate is fixed to the project rate, and warns that the actual file format may differ from the extension. It also describes the return structure (verified block and warning).

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 clear sections including mandatory instructions, acceptable locations, parameter details, and behavioral notes. It uses bold for emphasis. However, it is slightly verbose, repeating the prohibition of saving to the home folder twice. Nonetheless, every sentence adds value.

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?

For a tool with 3 parameters and no output schema or annotations, the description is exceptionally complete. It covers all parameter semantics, behavioral quirks of the underlying application, and the return structure. Given the potential for confusion with export, the description leaves no gaps.

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?

Despite 0% schema description coverage, the description adds rich meaning: it explains that 'path' determines format via extension, requires absolute path; 'num_channels' options (1=mono, 2=stereo); and 'whole_project' default behavior (selects all tracks and timeline) and when to set False. This far exceeds the schema's minimal information.

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 'Export the project audio to a file. Format is determined by file extension,' which is a specific verb+resource combination. It distinguishes itself from sibling tools like 'project_import_audio' and 'project_export_labels' by focusing on audio export.

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

Usage Guidelines5/5

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

The description provides comprehensive usage guidelines: it mandates informing the user of the save location, specifies acceptable subfolders (Music, Documents, Desktop), prohibits saving to the home folder root, and explains when to set 'whole_project' to False. It also directs the agent to call 'get_default_export_folder' if no path is specified.

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/robworks-code/audacity-mcp-max'

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