Skip to main content
Glama

delete

Destructive

Remove a track, return track, device, clip, or scene only when the exact name matches; one undo step restores it.

Instructions

Delete a track, return track, device, clip (t0/s2) or scene (s2).

Give its current name as a check: without the right name nothing is deleted. One undo step; undo brings it back.

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": {
      "target": "<target>",
      "name": "<name>"
    },
    "name": "delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe exact name of what you delete, as a check (read it first). A wrong name deletes nothing and the error shows the real name.
targetYesWhat to act on: a track (t0, rA), a device (t0/d1, t0/d0/c1/d0), a clip (t0/s2 = the clip in slot 2 of t0) or a scene (s2).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds real value beyond them: the name acts as a guard so a mismatch deletes nothing, the error surfaces the real name, and deletion is a single undo step that can be reversed. This is meaningful context that annotations cannot express.

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?

Three short sentences, front-loaded with the target types and followed by the guard and undo behavior; nothing is wasted. The name-check sentence overlaps slightly with the schema's parameter description, but it reinforces rather than pads.

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?

For a two-parameter destructive tool with full schema coverage and annotations declaring destructiveness, the description covers what gets deleted, how the target is addressed, the safety check, and reversibility. No output schema exists, and none of the remaining behavior (undo semantics, error on mismatch) is left implicit.

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?

Schema coverage is 100%, so both the name and target parameters are already fully documented, including the t0/s2 and s2 syntax examples. The description reiterates the name-as-check semantics and target forms but adds no format or edge-case detail the schema lacks, so it sits at the baseline.

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 (delete) and enumerates the exact resource types it can remove (track, return track, device, clip t0/s2, scene s2). An agent can immediately tell this is the removal tool and map its target syntax to the right object type, with no ambiguity against siblings like update_clip or update_track.

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?

It gives concrete invocation guidance ('give its current name as a check: without the right name nothing is deleted') and mentions undo reversibility, which helps the agent call it safely. However, it never states when to use this versus modifying an object with update_* or when not to use it; the guidance is about correct invocation rather than tool selection.

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