Node Manage
node_manageManipulate Godot node trees: delete, duplicate, rename, reorder, reparent nodes, manage groups, read hierarchy, and toggle editable children on instanced scenes.
Instructions
Node tree manipulation (delete, duplicate, rename, reorder, reparent, groups, hierarchy reads).
Resource forms (prefer for active-session reads): godot://node/{path}/properties, godot://node/{path}/children, godot://node/{path}/groups
Ops: • get_children(path) Direct children of a node (name, type, path each). • get_groups(path) Group names the node belongs to. • delete(path, scene_file="") Remove the node. Cannot delete scene root. Undoable. • duplicate(path, name="", scene_file="") Deep-copy a node + children as a sibling. Cannot duplicate scene root. • rename(path, new_name, scene_file="") Rename a node. Sibling-name collision and "/" / ":" / "@" rules apply. • move(path, index, scene_file="") Reorder among siblings. Index 0 = first. • reparent(path, new_parent, scene_file="") Move under a new parent. Children preserved. Cannot move into descendants. • set_editable_children(path, editable, scene_file="") Explicitly enable/disable Editable Children on an instanced scene root. Undoable when changed. Ancestors are never enabled implicitly. Disabling refuses saved child overrides, nested editable instances, attachments or signals that would be lost on save. Revert those first. • add_to_group(path, group, scene_file="") Add the node to a group. • remove_from_group(path, group, scene_file="") Remove the node from a group.
All write ops accept the optional scene_file guard — if non-empty, the
mutation fails with EDITED_SCENE_MISMATCH when the editor's current scene
doesn't match.
Writes inside non-editable scene instances are rejected before mutation. Use set_editable_children explicitly or edit the source scene. Deleting, renaming, reparenting, or reordering instance-owned nodes requires editing the source scene even when Editable Children is enabled.
Canonical call shape: {"op": "<verb>", "params": {...}}. Flat op parameters are accepted as a compatibility alias when the client transmits them; op and session_id remain top-level.
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": {
"op": "<op>"
},
"name": "node_manage"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| params | No | ||
| session_id | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||