Skip to main content
Glama

create_audio_track

Add an audio track to hold samples, stems, or recordings, inserting it at a chosen index or after the last track.

Instructions

Add an audio track (for samples, stems, recordings).

Parameters:

  • index: Where to insert it (-1 = after the last track)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_audio_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says a track is added. It does not say whether the new track becomes selected, what default name/volume it gets, whether the operation is undoable, or whether the call returns the created track — all material 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose sentence followed by a short labeled parameter note; there is no filler. It could be tightened further by folding the index explanation into prose, but the structure is clear and the size is appropriate.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but for an unannotated mutation tool the definition should still disclose placement side effects and preconditions. With zero annotation coverage and 0% schema description coverage, the definition leaves too much for the agent to infer.

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 0%, and the description does compensate for the single parameter by explaining the -1 sentinel as "after the last track", which the schema alone does not convey. However, it says nothing about what a non-negative index does when it exceeds the existing track count, so the semantics are only partially covered.

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?

States a specific verb and resource ("Add an audio track") and the parenthetical "(for samples, stems, recordings)" signals it is for audio material rather than MIDI. It stops short of naming create_midi_track as the contrasting sibling, so differentiation is implied rather than explicit.

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 statement of when to use this versus create_midi_track, or whether the project must already exist or contain tracks. The parenthetical hints at intended content type but gives no conditions or exclusions an agent could act on.

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

Deploy Server

Other Tools