Skip to main content
Glama

duplicate_track

Duplicate a regular track with its devices, clips, and mixer settings; the copy is placed directly after and selected. Optionally assign a name.

Instructions

Duplicate a regular track with its devices, clips and mixer settings; the copy goes right after it and is selected. Optionally name the copy. Live cannot duplicate return or master tracks.

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": {
      "track": "<track>"
    },
    "name": "duplicate_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
trackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds valuable behavior beyond that: where the copy lands (right after the original), that it becomes selected, and the return/master track exclusion. It stops short of saying what happens on name collision or whether the original is untouched.

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 short sentences, front-loaded with the action and scope, then the constraint. No filler; every clause carries information an agent can act on.

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 a 2-parameter mutation with no output schema, the description covers scope, side effects (selected, adjacent placement), and the key restriction. It is only incomplete on the `track` identifier format, which matters given 0% schema coverage.

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%, so the description must carry the parameters. It covers naming ("Optionally name the copy") but leaves `track` ambiguous — the anyOf integer|string allows index or name and the description never says which form is accepted.

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?

Specific verb+resource ("Duplicate a regular track") with explicit scope: devices, clips, and mixer settings are included in the copy. Naming "regular track" plus the note that return/master tracks cannot be duplicated distinguishes it clearly from siblings like duplicate_clip, duplicate_scene, and duplicate_device.

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?

States a hard precondition (Live cannot duplicate return or master tracks), which prevents a whole class of failed calls, and describes the resulting placement/selection. It does not, however, explicitly route the agent between this and duplicate_scene/duplicate_clip for adjacent tasks.

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