Skip to main content
Glama

Delete layer

delete_layer
Destructive

Permanently delete one or more named layers from a committed project scene; optionally close timeline gaps for a single layer. Selector-based and empty-project deletions are refused.

Instructions

Deterministic edit: permanently delete one or more named layers of a project, committed immediately. close_gap: true ripples the timeline closed and works with a single layer_id only. Selectors such as "all" or "@…" are refused, and so is a delete that would leave the project empty. To hide a layer temporarily use update_layer with {"visible": false} instead.

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": {
      "project_id": "<project_id>"
    },
    "name": "delete_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layer_idNoOne layer to delete.
close_gapNoRipple later layers left to close the gap (single layer_id only).
layer_idsNoSeveral layers to delete (alternative to layer_id).
project_idYesProject whose committed scene is edited.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes further: deletion is permanent and committed immediately, close_gap ripples the timeline, and two classes of requests are rejected outright. That is genuine behavioral context an agent could not derive from the annotation flags alone.

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?

Four sentences, each carrying a distinct constraint: what it does, the close_gap caveat, the refusal rules, and the safer alternative. The action and its permanence are front-loaded, with no filler.

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 destructive four-parameter mutation with no output schema, the description covers irreversibility, ripple behavior, input rejection rules, and the non-destructive alternative. Nothing an agent needs to call it safely 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?

Schema coverage is 100%, and the schema already documents layer_id, layer_ids as an alternative, and the close_gap single-layer restriction. The description restates those constraints ('one or more named layers', 'close_gap ... works with a single layer_id only') without adding format or validation detail, so it lands 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 and resource ('permanently delete one or more named layers of a project') and pins down the mode ('Deterministic edit... committed immediately'). The closing sentence distinguishes it from update_layer, so an agent can separate deletion from temporary hiding without inspecting either schema.

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?

Explicitly names the alternative ('To hide a layer temporarily use update_layer with {"visible": false}') and states the refusal conditions: selector syntax like 'all' or '@…' and any delete that would empty the project. When-to-use, when-not-to-use, and the substitute are all present.

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