Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

batch_delete

Destructive

Remove multiple objects from your Blender scene in a single operation. Confirmation is required to prevent accidental deletions.

Instructions

Delete multiple objects at once. Confirm required.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
objectsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With destructiveHint=true already indicating harm, the description adds the important behavioral note 'Confirm required', meaning the confirm parameter must be true to execute. This provides additional context beyond the annotation, though it doesn't detail what happens if confirm is false or confirm irreversibility.

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?

The description is two short, front-loaded sentences with no filler. Every word contributes to understanding the tool's core behavior and safety requirement.

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 destructive batch operation with an output schema, the description covers the essential purpose and confirmation requirement. However, it omits explicit details about the no-op behavior when confirm is false, though this is inferable. Overall, adequate but not exhaustive.

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 0%, and the description only partially compensates: 'Confirm required' clarifies the confirm parameter's role, but the objects parameter is only implied via 'multiple objects' without explaining that it's an array of identifiers. The description adds some meaning but leaves key parameter semantics underspecified.

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?

The description 'Delete multiple objects at once' clearly states the verb (delete), resource (objects), and batching scope ('multiple', 'at once'). This distinguishes it from sibling tools like delete_object, which handles single objects.

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

Usage Guidelines4/5

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

The phrase 'multiple objects at once' conveys that this tool is for bulk deletion, implying use when deleting more than one object. However, it does not explicitly mention alternatives or when not to use it (e.g., for single object use delete_object), so it lacks explicit exclusions.

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