Skip to main content
Glama
Sign In
Blender MCP Ultra

Blender MCP Ultra

by 3bdull4h2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

batch_delete_objects

Delete multiple Blender objects at once in a single call, reducing repetitive actions and streamlining scene cleanup.

Instructions

Delete multiple objects in one call.

Args: names: List of object names to delete.

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

Input Schema

NameRequiredDescriptionDefault
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It only says 'Delete multiple objects', implying a destructive operation but not mentioning any side effects, failure modes, partial deletion, or whether it's undoable. No detail on handling invalid names.

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 concise, with two sentences and no filler. The main action is front-loaded.

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

Completeness2/5

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

For a batch delete operation with no annotations and no output schema, the description is sparse. It lacks information about error handling, atomicity, and how it relates to other deletion tools, making it incomplete for an agent to call confidently.

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?

The description explains the 'names' parameter as 'List of object names to delete', which adds meaning beyond the schema's bare array type. However, it doesn't elaborate on formatting, case sensitivity, or whether non-existent names are handled.

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 states 'Delete multiple objects in one call' – a specific verb and resource, clearly distinguishing it from the singular delete_object and other batch_* tools that perform different actions.

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?

No guidance is provided on when to use this tool versus alternatives like delete_object or other batch operations. There is no mention of criteria such as 'use for bulk deletion' or 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