Skip to main content
Glama

get_arrangement_clips

Retrieve a track’s Arrangement clips in time order, including each clip’s position, length, and type, to get the clip_index values other tools use.

Instructions

The clips a track has in the Arrangement, in time order, with their position, length and type. Their order is the clip_index other tools use.

Parameters:

  • track_index: The track

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": "get_arrangement_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses what is returned (clips with position, length, type, in time order) and the meaning of the ordering, which is real added value, but says nothing about error behavior for an invalid track_index, empty tracks, or whether hidden/disabled clips are included.

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 with the core purpose, then a short parameter section; no filler sentences. The separate 'Parameters:' heading is slightly heavy for a single parameter, but nothing is wasted.

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?

An output schema exists, so return values needn't be spelled out, and the ordering/clip_index note covers the main cross-tool dependency. However, for a tool whose only input is an opaque integer index, the definition leaves the caller without the indexing convention or provenance needed to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description must compensate. It only offers 'track_index: The track', which restates the name and gives no indexing base (0- vs 1-based) or hint about how to obtain a valid track index from another tool.

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?

The description states a specific verb and resource ('the clips a track has in the Arrangement') and adds scope details: time order, position, length, and type. It implicitly distinguishes Session clips from Arrangement clips, but it never names a sibling tool to contrast against, so it stops short of a 5.

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?

There is no explicit 'use this when / not when' language, and no alternative tool is named. The one genuinely useful usage cue is the statement that the returned order is the clip_index other tools use, which tells an agent how to chain this call, but the conditions for choosing it over siblings like arrangement_overview are left 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