Skip to main content
Glama

delete_clip

Empties a Session slot on a given track so the slot is free again, for example before placing a new clip with create_clip, which refuses occupied slots.

Instructions

Empty a Session slot (create_clip refuses occupied slots).

Parameters:

  • track_index: The track

  • clip_index: The Session slot to empty

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

Input Schema

NameRequiredDescriptionDefault
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a destructive operation, yet it says nothing about what is destroyed (clip content, devices, notes?), whether the action is reversible, or what happens when called on an already-empty slot. The one useful behavioral hint is that create_clip refuses occupied slots, which explains why this tool exists.

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 lines with the purpose front-loaded and a compact parameter list; nothing is wasted. It is terse to the point of under-specification, but the structure itself is clean.

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

Completeness2/5

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

For a destructive tool with no annotations and zero schema description coverage, the definition leaves out error behavior, idempotence on empty slots, and what data is lost. An output schema exists, so return values need not be explained, but the mutation semantics remain inadequately covered.

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%, so the description must compensate, and it barely does: "The track" and "The Session slot to empty" restate the schema titles (Track Index, Clip Index) with only a hint that clip_index refers to a Session slot. Indexing base, valid ranges, and the relationship between the two indices are left unspecified.

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?

"Empty a Session slot" gives a specific verb+resource and the word "Session" implicitly separates it from the arrangement-oriented sibling delete_arrangement_clip. It stops short of naming that sibling explicitly, so an agent must infer the distinction rather than being routed to it.

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?

The parenthetical "create_clip refuses occupied slots" implies the main use case: freeing a slot before creating a clip there. There is no explicit when-to-use statement, no mention of delete_arrangement_clip as the alternative for arrangement clips, and no note on whether the slot must be occupied.

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