Skip to main content
Glama

Create clip launcher

create_clip_launcher

Build a grid of clip buttons that fire cues for live scene switching. Supports instant jumps or crossfades over a set time.

Instructions

Build an Ableton-style clip launcher: a grid panel (Container COMP) of clip buttons, one per named cue (from manage_cue), for fast hands-on scene switching during a live set. Open the container in Perform/Panel mode and tap a clip to fire its cue — instantly, or (with morph_time) crossfading to it over N seconds (eased, the same engine manage_cue uses). Store the cues with manage_cue / create_control_panel first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comp_pathNoControl COMP that holds the cues (manage_cue) and custom params. The launcher panel is built inside it and its buttons fire that COMP's cues./project1
nameNoName of the launcher panel container to build.launcher
cuesYesCue names (stored with manage_cue) to lay out in the grid, in order. Each becomes a clip button labelled with its cue name.
rowsNoGrid row count. Defaults so rows*cols covers all cues (derived from cues length).
colsNoGrid column count. Defaults to ceil(sqrt(cues)) when omitted (derived from cues length).
morph_timeNo0 = each button jumps instantly to its cue; >0 = every button crossfades to its cue over this many seconds (eased morph, same engine as manage_cue).
Behavior4/5

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

Annotations indicate non-read-only, non-destructive, and open-world. The description adds behavioral details: the launcher fires cues instantly or with a crossfade (morph_time), and it is built inside a specified Control COMP. No contradictions observed.

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?

The description is two sentences, front-loaded with the main purpose, and includes both usage instructions and a prerequisite note. Every sentence adds value without redundancy.

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 tool with 6 parameters and no output schema, the description covers the essential behavior (grid of clip buttons, instant vs. morph). It references related tools (manage_cue, create_control_panel) and explains the interaction mode. Minor gap: no mention of layout defaults beyond 'derived from cues length'.

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?

Schema coverage is 100% and parameters are well-described. The description adds meaning by explaining the grid layout concept and morph_time behavior (crossfade, eased). This goes beyond the schema, which lists defaults and constraints.

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 description clearly states it builds an Ableton-style clip launcher grid panel with buttons for each named cue. It uses specific verbs ('Build', 'Open', 'tap') and resources ('Container COMP', 'cue'), distinguishing it from other create_* tools.

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?

The description provides clear context for when to use the tool (after storing cues with manage_cue/create_control_panel) and how to interact with the result (open in Perform/Panel mode). It does not explicitly list when-not or alternatives, but the guidance is sufficient.

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

Install Server

Other Tools

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/Pantani/tdmcp'

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