Skip to main content
Glama

remove

Deletes a shot or entire scene by ID, preventing deletion of a scene’s only shot or the last scene. Returns { done } and records one undo step.

Instructions

Remove a shot or a whole scene by id. A scene's only shot can't be removed alone (remove the scene), and the last scene can't go. One undo step for the person. Returns { done }. To take a person or object out of a shot, use cast with op remove.

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": {
      "id": "<id>"
    },
    "name": "remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesShot id or scene id (from get_project).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / id / description
      Previous value: -"Shot id or scene id."New value: +"Shot id or scene id (from get_project)."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses that the action is undoable in one step for the person and that it returns { done }, which is the key safety context for a removal tool. It does not spell out what happens to a scene's contained shots when the scene itself is removed, which is the remaining behavioral gap.

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 short sentences, front-loaded with the action and resource, then constraints, then undo/return behavior, then the sibling redirect. Every clause carries information an agent needs.

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 one-parameter mutation with annotations, the definition covers the action, the guard rails, reversibility, and the return shape. Only the side effects on dependent data when removing a whole scene are 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% and the single id parameter is already documented as accepting either a shot id or a scene id from get_project. The description restates that polymorphism without adding format, validation, or lookup detail beyond the schema, so baseline 3 applies.

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?

"Remove a shot or a whole scene by id" gives a specific verb, two concrete resource types, and the selector. The closing sentence distinguishes it from the sibling 'cast with op remove', so an agent can pick the right tool without opening 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?

It states explicit preconditions (a scene's only shot can't be removed alone, the last scene can't be removed) and names the correct alternative for a related intent (use cast with op remove to take a person or object out of a shot). It covers both when-not and the alternative route.

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