Skip to main content
Glama

edit_warp_markers

Add, move, or remove warp markers on a warped audio clip to correct timing. Pin sample moments to beats, shift existing markers, or delete unwanted ones by beat time.

Instructions

Edit the warp markers of a warped audio clip (Live 11+), in this order: remove, then move, then add. get_clip_warp shows the current ones.

Parameters:

  • track_index: An audio track

  • clip_index: Session slot, or position in get_arrangement_clips

  • location: "session" (default) or "arrangement"

  • add: [{"beat_time": 8.0, "sample_time": 3.66}] pins a moment of the file (seconds) to a beat

  • move: [{"beat_time": 8.0, "beat_time_distance": 0.25}] shifts that marker by some beats

  • remove: [8.0, 16.0] beat times of markers to delete

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>",
      "clip_index": "<clip_index>"
    },
    "name": "edit_warp_markers"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNo
moveNo
removeNo
locationNosession
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the Live 11+ requirement and the deterministic operation order, which affects outcomes when the same marker is both moved and removed, but says nothing about whether the clip must be warped, failure handling, atomicity, or undo grouping.

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?

Front-loaded with purpose and ordering rule, then a compact per-parameter block with inline examples. No redundant restatement of the tool name and no filler sentences.

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 high-complexity tool with nested object arrays and 0% schema coverage, the description supplies ordering, units, and examples, and an output schema exists so return values need not be described. Minor gaps remain around error conditions and preconditions on the clip's warp state.

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?

Schema description coverage is 0% and the raw schema types are bare ('array of objects with number values'), so the description does the entire job: it defines the beat_time/sample_time pairing for add, beat_time_distance for move, a plain beat-time list for remove, and the session/arrangement distinction with its default. Concrete JSON examples remove ambiguity about key names and units (seconds vs beats).

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?

States a specific verb and resource ('Edit the warp markers of a warped audio clip') plus a version constraint (Live 11+), and points at get_clip_warp for reading current state. An agent can distinguish this from the read-side sibling without opening either schema.

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?

Explicitly tells the agent to inspect existing markers via get_clip_warp first, and the stated apply order (remove, then move, then add) is a real usage constraint. It does not name when to prefer this over set_clip_warp, so alternatives remain implicit.

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