Skip to main content
Glama

delete_collection

Remove a named collection from a Blender scene by specifying its name, with optional confirmation to prevent accidental deletion.

Instructions

Delete a collection.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/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, and it discloses nothing. It does not say whether deletion is irreversible, whether contained objects are deleted or orphaned, what the `confirmed` flag gates, or what permissions are required — all critical for a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is not verbose, but it is under-specified rather than concise. There is no structure to front-load because there is essentially no content.

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

Completeness1/5

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

For a destructive, destructiveHint-less tool with an unexplained confirmation parameter and an existing output schema, the description omits everything an agent needs: effect on contained data, irreversibility, and confirmation semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with two parameters, and the description adds no meaning. The purpose of `confirmed` (a safety gate?) and the expected format of `name` (exact match? path?) are left entirely unexplained in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Delete a collection" restates the tool name and nothing more. It gives no indication of what a collection is in this system or how this differs from siblings such as delete_objects or delete_geometry, so the agent learns nothing beyond the verb already encoded in the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no prerequisites, no note about when deletion is appropriate versus emptying a collection or moving its contents with move_object_to_collection, and no mention of the destructive nature that would make an agent cautious.

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