Skip to main content
Glama

roblox_manage

Manipulate Roblox Studio scene instances to create, update, delete, clone, reparent, reset pivots, and manage selections.

Instructions

Mutate instances in the Roblox Studio scene.

Actions:

  • "create": Create a new instance. Params: className (required), name, parent (path), properties (object).

  • "create_multiple": Batch-create instances. Params: parent (default path), instances (array of {className, name, parent?, properties?}).

  • "update": Update properties on an existing instance. Params: path (required), name, properties (object).

  • "reset_pivot": Reset a Model's WorldPivot to its bounding box center, or a BasePart's PivotOffset to zero. Params: path (required). Use this when positioning/PivotTo is behaving unexpectedly — a stale WorldPivot far from the geometry is a common cause. Automatically done on toolbox insert, but useful for debugging.

  • "delete": Destroy an instance. Params: path (required).

  • "clone": Clone an instance tree. Params: path (required), name, parent.

  • "reparent": Move an instance to a new parent. Params: path (required), newParent (required).

  • "set_selection": Set the Studio selection. Params: paths (array of paths).

  • "undo": Undo last action.

  • "redo": Redo last undone action.

Property format: vectors as {X,Y,Z}, colors as {R,G,B} (0-1 range), booleans, strings, numbers. Example: {"Position": {"X":0,"Y":5,"Z":0}, "Size": {"X":4,"Y":1,"Z":4}, "Anchored": true, "Material": "Neon", "Color": {"R":1,"G":0,"B":0}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich mutation to perform
classNameNoClass to create (e.g. "Part", "Model", "Folder", "SpawnLocation")
pathNoTarget instance path
nameNoInstance name
parentNoParent path (default Workspace)
newParentNoNew parent path (for reparent)
propertiesNoProperties to set/update
instancesNoArray of {className, name, parent?, properties?} for create_multiple
pathsNoInstance paths (for set_selection)
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it explains what 'reset_pivot' does for debugging, mentions that it's 'automatically done on toolbox insert,' describes property formats with examples, and clarifies that actions like 'delete' destroy instances. However, it doesn't cover error handling, permissions, or rate limits.

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?

The description is appropriately sized and front-loaded with the core purpose, followed by a structured list of actions with their parameters. Every sentence earns its place, though the property format explanation could be slightly more concise. Overall, it's well-organized and efficient.

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

Completeness4/5

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

Given the tool's complexity (9 parameters, nested objects, no output schema, no annotations), the description is quite complete. It covers all actions, parameter semantics, and behavioral context. The main gap is the lack of output information, but this is mitigated by the detailed input guidance. It adequately compensates for the missing structured data.

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 description coverage is 100%, so the baseline is 3. The description adds significant value by explaining parameter usage per action (e.g., 'className (required)' for create), providing property format examples, and clarifying default values like 'parent (default path)' for create_multiple. This goes well beyond what the schema provides.

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 starts with a clear purpose statement: 'Mutate instances in the Roblox Studio scene.' It specifies the exact action (mutate) and resource (instances in Roblox Studio scene), and distinguishes from sibling tools like roblox_get (likely read-only) and roblox_playtest (likely testing-focused).

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?

The description provides clear context for when to use specific actions (e.g., 'Use this when positioning/PivotTo is behaving unexpectedly' for reset_pivot), but doesn't explicitly state when to choose this tool over alternatives like roblox_scene or roblox_toolbox. It offers good intra-tool guidance but lacks inter-tool comparison.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paralov/roblox-studio-opencode-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server