Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_collection

Deletes a Blender collection. Set delete_objects to true to remove its objects, or false to unlink and keep them.

Instructions

Delete a collection.

Args: collection_name: Name of the collection to delete. delete_objects: If True, also delete all objects in the collection. If False, objects are unlinked but kept in the scene.

Returns: Confirmation dict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delete_objectsNo
collection_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • addedInput schema / properties / collection_name
      Added value: +{
+  "title": "Collection Name",
+  "type": "string"
+}
    • removedInput schema / properties / name
      Removed value: -{
-  "title": "Name",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "collection_name"
+]
  2. Changed1 schema field changedv1.2.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "delete_collectionDictOutput",
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a genuinely important behavioral trait: delete_objects=True destroys contained objects, while False unlinks them and keeps them in the scene, and it states the return is a confirmation dict. It is silent on permissions, nested-collection behavior, and whether deletion is undoable, which are meaningful gaps for a destructive operation.

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?

It is short and front-loads the purpose, and every substantive sentence earns its place. The docstring scaffolding ('Args:', 'Returns:') is mild structural noise but does not obscure the content.

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

Completeness3/5

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

An output schema exists, so return-value detail is legitimately omitted, and the key destructive semantics of delete_objects are covered. For a mutation tool with zero annotations, however, the description should also address nested collections, permission requirements, or failure modes to be fully complete.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it largely does: it names both parameters and gives the non-obvious semantics of delete_objects (delete vs. unlink while preserving objects in the scene). collection_name is only restated, and there is no note on error behavior when the name doesn't exist.

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?

The description states a specific verb and resource ('Delete a collection'), which is unambiguous about what the tool does. It does not, however, distinguish itself from siblings like delete_object, delete_material, or delete_scene beyond the resource name. Clear but no sibling differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as create_collection, move_to_collection, or delete_object, nor any prerequisite or caution about irreversibility. The parameter semantics are explained, but not the usage context.

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