Skip to main content
Glama

delete_object

Removes a single object from the Blender scene by name, with optional confirmation required for destructive actions. Use it to clear specific objects before modeling or rendering.

Instructions

Delete a single object (requires confirmed=true when confirm_destructive is on).

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_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 correctly implies a destructive mutation and usefully discloses a confirmation gate, but says nothing about irreversibility, whether children/instances are affected, or failure modes such as deleting a linked object.

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?

A single front-loaded sentence with no filler. The compression costs some clarity, though: the referenced 'confirm_destructive' flag is never defined, leaving the conditional ambiguous.

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?

The presence of an output schema removes the need to describe return values, which lightens the load. For a destructive, unannotated mutation with 0% schema coverage, however, the definition leaves out consequences and error conditions an agent needs before invoking it.

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

Parameters2/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 for both parameters. It explains 'confirmed' only by reference to an external 'confirm_destructive' setting whose location and default are unstated, and it adds nothing about 'name' (identifier vs. display name, uniqueness, lookup failure).

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?

States a specific verb and resource ('Delete a single object') and the word 'single' implicitly separates it from the batch sibling delete_objects. It stops short of naming the alternative explicitly, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The parenthetical gives a conditional precondition (confirmed=true when confirm_destructive is on), which is real usage guidance. But it never says when to prefer this over delete_objects or delete_collection, nor what happens if the flag is required and omitted.

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