Skip to main content
Glama

duplicate_track

Copy a track, including its clips and devices, and insert the copy immediately after the original.

Instructions

Copy a track with its clips and devices; the copy goes right after it.

Parameters:

  • track_index: The track to copy

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_index": "<track_index>"
    },
    "name": "duplicate_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing what is duplicated (clips and devices) and where the copy lands (immediately after the original). It is silent on side effects an agent might care about, such as whether the new track becomes selected, how routing/sends are handled, and whether the operation is undoable. Return values are covered by the output schema, so that omission is acceptable.

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?

Two short, front-loaded sentences: the behavior statement first, then the parameter gloss. Nothing is redundant, though the 'Parameters:' block is slightly formal overhead for a single argument.

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?

For a single-parameter mutation with an output schema and no annotations, the essentials are present but not complete: indexing convention, selection side effects, and whether device/clip state is deep-copied or referenced remain unaddressed.

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

Parameters4/5

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

Only one parameter and schema coverage is 0%, so the description must carry the meaning – and it does, stating that track_index identifies the track to copy. It still omits indexing base (0- vs 1-based) and valid range, which would matter for correct invocation.

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 ('Copy a track') plus the exact behavior: clips and devices are included and the copy is placed immediately after the source. That distinguishes it adequately from create_audio_track/duplicate_scene by name, though it never explicitly contrasts them.

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

Usage Guidelines3/5

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

Usage is only implied: the mention of copying clips and devices signals when to prefer this over creating a fresh track, but there is no explicit 'use this when...' or 'do not use for...' guidance and no alternatives named.

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