Skip to main content
Glama

get_clip

Read-onlyIdempotent

Read a Session clip's properties—length, loop, warp, pitch, markers, flags—from a track slot. Returns has_clip: false for empty slots instead of failing.

Instructions

Read one Session clip's properties: length, loop, warp, pitch, markers, flags.

Checks the slot is filled first, because a clip only exists while its slot
has one and every property read would otherwise fail one by one.

Returns:
    Dictionary with ``has_clip``, and where that is true the clip path, whether
    it is MIDI, and the property fields. An empty slot answers ``has_clip:
    false`` and says so rather than failing.

Note:
    Notes are not properties. Use ``read_clip_notes``. Automation is not a
    property either. Use ``read_automation``.

    ``warping``, ``warp_mode`` and ``pitch_coarse`` are reachable only through a
    generic path, because a per-command bridge has no command for them and a
    missing command is easily mistaken for a missing capability
    (docs/architecture.md, 'the restart tax'). Each was read, written, read back
    and restored on 2026-08-29 against Live 12.4.5, and all three rows are
    ``verified``. ``pitch_fine`` is read-verified only, with no write attempted
    on it, and the integer mapping behind ``warp_mode`` is still a hypothesis:
    confirm it against ``clip.available_warp_modes``, which is the authoritative
    per-clip list.

    Writing ``warping`` invalidates every time field this tool just returned. On a
    1.14-unit audio clip at 120 BPM, turning warping on took ``loop_end`` from 0.5704
    to 1.1408 and ``end_marker`` from 1.1408 to 2.2816, both doubled, while ``length``
    did not follow. At 60 BPM the same toggle moved neither. The mechanism is not
    established and is not claimed. What is established is that the numbers move and
    that the factor tracks the tempo. Call this again after any write to ``warping``
    rather than reusing what it said before.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYesClip slot index in track.clip_slots, counted from 0. A slot index is the scene the clip sits in, so slot 2 is the third scene down.
trackYesTrack index in song.tracks, counted from 0.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / slot / description
      Added value: +"Clip slot index in track.clip_slots, counted from 0. A slot index is the scene the clip sits in, so slot 2 is the third scene down."
    • addedInput schema / properties / track / description
      Added value: +"Track index in song.tracks, counted from 0."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this read-only and idempotent, but the description adds material behaviors: slot-empty handling returns has_clip:false instead of failing, and property reads are guarded by a filled-slot check. It also discloses verification status of returned fields and the time-field invalidation caveat after warping writes, which annotations could not convey. No contradiction with readOnlyHint=true exists because the description describes an external write, not the tool writing.

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?

The description is long, but the core purpose is front-loaded in the first sentence, followed by clearly separated return and note sections. While every section is relevant, the detailed empirical warping example and verification history add notable length and could be trimmed without losing the essential warning. It remains well-structured.

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

Completeness5/5

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

The description covers prerequisite behavior (filled slot check), exact return semantics including empty-slot handling, adjacent data routes, and the only significant stale-data hazard with a concrete directive to re-call. Given the tool's moderate complexity and the presence of an output schema, nothing needed for correct agent invocation is missing.

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?

The input schema already documents both track and slot parameters with clear semantics and 100% coverage, including the 0-based indexing and slot-as-scene meaning. The description adds no new parameter-level detail, so it stands at the schema-covered baseline. It references 'slot' in the filled-check context but not in a way that deepens parameter understanding.

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?

The first sentence specifies a concrete read operation on a Session clip and lists the exact property groups returned. It also names the sibling tools for adjacent data (read_clip_notes, read_automation), directly distinguishing this tool from those. This makes the tool's scope unambiguous.

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

Usage Guidelines5/5

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

It explicitly says to use read_clip_notes for notes and read_automation for automation, which are the closest alternatives, and clarifies what get_clip is not responsible for. It also advises re-calling after a warp write because cached property values may be stale. This gives an agent clear selection and invocation guidance.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/romanstark/live-maestro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server