Skip to main content
Glama

editor_duplicate_actor

Duplicate a loaded actor with its children and scripts into a scene or under a parent actor, then return the new actor's live details and record an Undo step.

Instructions

Duplicates a loaded actor, with its children and scripts, into a loaded scene or under a loaded parent actor. Returns the live details of the duplicate. Set exactly one of sceneId and parentId, and set the other to null. name is the name of the duplicate. Its children keep their names. translation, orientation and scale set the world transform of the duplicate. The source actor does not change. The editor records an Undo step. The scene stays unsaved until editor_save. To make a new actor of a type, use editor_create_actor. To move an actor to a different parent, use editor_reparent_actor.

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": {
      "actorId": "<actorId>",
      "name": "<name>",
      "sceneId": "<sceneId>",
      "parentId": "<parentId>",
      "translation": "<translation>",
      "orientation": "<orientation>",
      "scale": "<scale>"
    },
    "name": "editor_duplicate_actor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scaleYes
actorIdYes
sceneIdYes
parentIdYes
orientationYes
translationYes

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
tagsYes
layerYes
sceneIdYes
scriptsYes
isActiveYes
parentIdYes
typeNameYes
layerNameYes
transformYes
mainThreadIdYes
localTransformYes
isActiveInHierarchyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: source actor unchanged, an Undo step is recorded, the scene stays unsaved until editor_save, children retain names, and it returns live duplicate details.

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?

Dense but front-loaded: core action first, then parameter rules, then side effects, then sibling routing. 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?

An output schema exists, so return format need not be explained; the description still covers destination rules, side effects, and persistence state, leaving nothing an agent needs to call it correctly.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description compensates by explaining the sceneId/parentId mutual exclusivity, that name applies only to the duplicate, and that translation/orientation/scale set the world transform. Only actorId's role as the source is left implicit.

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 ('Duplicates a loaded actor, with its children and scripts') plus the destination options, and explicitly distinguishes itself from editor_create_actor and editor_reparent_actor by name.

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 exclusivity rule ('Set exactly one of sceneId and parentId, and set the other to null') and routes the agent to sibling tools for the two adjacent operations.

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