Skip to main content
Glama

delete_instance

DestructiveIdempotent

Delete a Roblox instance and all its descendants by dot path from the edit copy, recorded as a single Studio undo step. Fails if the path does not resolve.

Instructions

Destroy an instance and all of its descendants in the edit copy. Recorded as one Studio undo step, so history undo brings it back while the undo stack lasts. For a checkpoint that outlives the undo stack, take a snapshot first. Fails if the path does not resolve.

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": {
      "path": "<path>"
    },
    "name": "delete_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesInstance to destroy. Dot path from the DataModel root, e.g. "Workspace.Map.Door" or "StarterGui.HUD.Frame". A leading "game." is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. "Part (2)".
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / path / description
      Added value: +"Instance to destroy. Dot path from the DataModel root, e.g. \"Workspace.Map.Door\" or \"StarterGui.HUD.Frame\". A leading \"game.\" is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. \"Part (2)\"."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint and readOnlyHint=false, but the description adds real behavior the schema does not: the deletion cascades to descendants, it is recorded as a single undo step, it is recoverable via history only while the undo stack lasts, and it fails when the path does not resolve. That is exactly the context an agent needs before an irreversible-looking mutation.

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?

Three short sentences, front-loaded with the destructive action and scope, then recoverability, then the durability alternative and failure mode. No sentence is filler.

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 two-parameter destructive mutation with no output schema, the description covers scope, reversibility window, a safer alternative, and the failure mode. There is nothing an agent would need before calling it that is missing.

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%, with both parameters documented including path format and suffix handling, so the baseline is 3. The description only indirectly touches the path parameter via 'Fails if the path does not resolve' and adds no format or place-targeting detail beyond the schema.

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?

States a specific verb and resource ('Destroy an instance') plus scope ('and all of its descendants') and the operating context ('in the edit copy'). An agent can distinguish this from sibling tools like delete_snapshot or history 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 Guidelines4/5

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

Gives an explicit alternative with its condition: take a snapshot first if the checkpoint must outlive the undo stack. Also states the failure condition. It does not address when to prefer non-destructive alternatives (move/rename) or bulk removal via batch, but the core routing guidance is present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.