Skip to main content
Glama

clone_instance

Copy a Roblox Studio instance together with all its descendants and return the new copy's path, recorded as a single undo step. Choose a different parent to duplicate it elsewhere.

Instructions

Copy an instance with all its descendants and return the copy's path. Recorded as one Studio undo step. Instances with Archivable=false cannot be cloned. For many copies at once use batch with several clone operations.

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": "clone_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesInstance to copy. 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.
parentPathNoParent for the copy. 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)". Omit to use the original's parent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / parentPath / description
      Added value: +"Parent for the copy. 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)\". Omit to use the original's parent."
    • addedInput schema / properties / path / description
      Added value: +"Instance to copy. 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.4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent mutation, and the description adds genuinely new behavior: the operation is atomic as a single Studio undo step, Archivable=false is a hard failure case, and the return value is the copy's path. It does not cover name-collision behavior on the clone or what happens if parentPath is invalid, but the annotation baseline is already covered with useful added context.

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?

Four short sentences, front-loaded with purpose then the return, then the constraint, then the alternative. Every sentence carries information; only minor tightening is possible.

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 3-parameter mutation with no output schema, the description covers purpose, atomicity, failure condition, return value, and the batch alternative — everything an agent needs to call it correctly and to know what comes back.

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%, so path, place, and parentPath (including the 'omit to use the original's parent' default) are already fully documented in the schema. The description adds no parameter-level detail beyond that, so it sits at the baseline for a fully documented 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 — copy an instance including all descendants — and adds the return value (the copy's path), which distinguishes it from create_instance (new object) and move_instance (relocation). The sibling reference to batch makes the boundary explicit.

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?

Gives an explicit alternative and the condition that selects it: 'For many copies at once use batch with several clone operations.' It also names a precondition (Archivable=false instances cannot be cloned), so the agent knows when the call will fail before attempting it.

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