Skip to main content
Glama

delete_actor

Destructive

Remove one actor from the editor level via the editor's undoable delete path and return its JSON. Use the internal name, not a label; selection is cleared.

Instructions

Remove one actor from the EDITOR level through the editor's own delete path (select + edactDeleteSelected), so it is transacted and undoable, and echo back the deleted actor's JSON. WARNING: two edges that bite: it matches the INTERNAL name only -- unlike set_actor_transform, an editor LABEL will not resolve -- and it clears the current selection as a side effect. It cannot touch PIE actors (editor world only), and the deletion lives in memory until save_level writes the .umap. Use batch_delete_actors for several at once.

Returns: { deleted_actor: actor JSON captured before the delete }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesActor's internal name (GetName), case-insensitive but WHOLE-string. Editor labels are NOT accepted here; resolve one first with find_actors_by_name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds rich behavioral context beyond those annotations: the delete is transacted and undoable, it clears the current selection, it matches internal names only, and the deletion lives in memory until save_level writes the .umap.

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 dense and front-loaded, starting with the action and following with critical caveats and the return shape. Every sentence earns its place, and the WARNING framing efficiently flags the two non-obvious edges.

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

Completeness5/5

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

For a destructive editor-only delete tool, the description covers side effects, persistence, name-resolution requirements, PIE exclusion, and the batch alternative. It also includes a Returns line even though no output schema exists, making it complete for correct invocation.

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 description coverage is 100%, and the single parameter is fully documented in the schema. The description reinforces that editor labels are not accepted but does not add syntax, format, or resolution details beyond what the schema already provides, so the baseline 3 applies.

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 a specific verb and resource: 'Remove one actor from the EDITOR level through the editor's own delete path...' and explicitly distinguishes the tool from batch_delete_actors. An agent can tell what this does without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use and when-not-to-use guidance: 'Use batch_delete_actors for several at once' and 'It cannot touch PIE actors (editor world only).' It also tells the agent to resolve names first with find_actors_by_name, covering the alternative workflow.

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