Roblox Studio MCP

Overview Schema Source Related Servers Discussions Admin

Create instances

create

Destructive

Construct Roblox instances with properties, attributes, and tags in a single undoable step. Nest children to build complete models, with property names validated against the Roblox API before sending to Studio.

Instructions

Creates instances with their properties, attributes and tags set at creation, as one undoable step.

Nest with children to build a whole model in a single call. That is both faster and safer than creating a parent and then addressing it: a new instance's path is not knowable until it exists, and same-named siblings make guessing it unreliable.

Property names are checked against the live Roblox API dump before anything is sent to Studio, so a typo comes back with the closest real names rather than an engine error.

Use script_create for Script, LocalScript and ModuleScript — it takes source directly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`studioId`	No	Target Studio; omit for the active one.
`instances`	Yes	Instances to create together as one undoable step.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.0Sep 24, 2026

changedInput schema / properties / instances / items / properties / children / description

Previous value: -"Instances to create inside this one. Build a whole model in one call rather than creating a parent and then addressing it by a path you have to guess."New value: +"Instances to create inside this one. Each takes the same fields as this entry (className, name, properties, attributes, tags, children), nested as deep as needed. Build a whole model in one call rather than creating a parent and then addressing it by a path you have to guess."

Changed5 schema fields changedv0.7.8Sep 23, 2026

removedInput schema / definitions

Removed value: -{
-  "__schema0": {
-    "properties": {
-      "attributes": {
-        "additionalProperties": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "number"
-            },
-            {
-              "type": "boolean"
-            },
-            {
-              "properties": {
-                "type": {
-                  "description": "Roblox type to store the attribute as. Needed for anything but a plain string, number or boolean — a bare string stays a string.",
-                  "enum": [
-                    "string",
-                    "boolean",
-                    "number",
-                    "BrickColor",
-                    "CFrame",
-                    "Color3",
-                    "ColorSequence",
-                    "Font",
-                    "NumberRange",
-                    "NumberSequence",
-                    "Rect",
-                    "UDim",
-                    "UDim2",
-                    "Vector2",
-                    "Vector3"
-                  ],
-                  "type": "string"
-                },
-                "value": {
-                  "description": "The value, written as the Properties panel shows it: \"0, 5, 0\".",
-                  "type": [
-                    "string",
-                    "number",
-                    "boolean"
-                  ]
-                }
-              },
-              "required": [
-                "type",
-                "value"
-              ],
-              "type": "object"
-            }
-          ]
-        },
-        "description": "Attributes to set, as name → value. A bare string, number or boolean is stored as-is; for any other type pass { type, value }, e.g. { type: \"Vector3\", value: \"0, 5, 0\" }. An empty string removes an attribute.",
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "children": {
-        "description": "Instances to create inside this one. Build a whole model in one call rather than creating a parent and then addressing it by a path you have to guess.",
-        "items": {
-          "$ref": "#/definitions/__schema0"
-        },
-        "type": "array"
-      },
-      "className": {
-        "description": "Concrete class to create, e.g. \"Part\", \"Folder\", \"Model\", \"SpawnLocation\".",
-        "type": "string"
-      },
-      "name": {
-        "description": "Name for the new instance.",
-        "type": "string"
-      },
-      "parent": {
-        "description": "Where to put it, e.g. \"Workspace\". Required at the top level only.",
-        "type": "string"
-      },
-      "properties": {
-        "additionalProperties": {
-          "type": [
-            "string",
-            "number",
-            "boolean"
-          ]
-        },
-        "description": "Properties to set, as name → value. Values are written the way Studio's Properties panel shows them: \"12, 0, 5\" for a Vector3, \"0.2, 0.6, 1\" for a Color3, \"Neon\" or \"Enum.Material.Neon\" for an enum, true/false for a bool.",
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "tags": {
-        "description": "CollectionService tags to add or remove.",
-        "properties": {
-          "add": {
-            "description": "CollectionService tags to add.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "remove": {
-            "description": "Tags to remove.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "type": "object"
-      }
-    },
-    "required": [
-      "className"
-    ],
-    "type": "object"
-  }
-}

removedInput schema / properties / instances / items / $ref
```
Removed value: -"#/definitions/__schema0"
```

addedInput schema / properties / instances / items / properties

Added value: +{
+  "attributes": {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "properties": {
+            "type": {
+              "description": "Roblox type to store the attribute as. Needed for anything but a plain string, number or boolean — a bare string stays a string.",
+              "enum": [
+                "string",
+                "boolean",
+                "number",
+                "BrickColor",
+                "CFrame",
+                "Color3",
+                "ColorSequence",
+                "Font",
+                "NumberRange",
+                "NumberSequence",
+                "Rect",
+                "UDim",
+                "UDim2",
+                "Vector2",
+                "Vector3"
+              ],
+              "type": "string"
+            },
+            "value": {
+              "description": "The value, written as the Properties panel shows it: \"0, 5, 0\".",
+              "type": [
+                "string",
+                "number",
+                "boolean"
+              ]
+            }
+          },
+          "required": [
+            "type",
+            "value"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "description": "Attributes to set, as name → value. A bare string, number or boolean is stored as-is; for any other type pass { type, value }, e.g. { type: \"Vector3\", value: \"0, 5, 0\" }. An empty string removes an attribute.",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "children": {
+    "description": "Instances to create inside this one. Build a whole model in one call rather than creating a parent and then addressing it by a path you have to guess.",
+    "items": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "className": {
+    "description": "Concrete class to create, e.g. \"Part\", \"Folder\", \"Model\", \"SpawnLocation\".",
+    "type": "string"
+  },
+  "name": {
+    "description": "Name for the new instance.",
+    "type": "string"
+  },
+  "parent": {
+    "description": "Where to put it, e.g. \"Workspace\". Required at the top level only.",
+    "type": "string"
+  },
+  "properties": {
+    "additionalProperties": {
+      "type": [
+        "string",
+        "number",
+        "boolean"
+      ]
+    },
+    "description": "Properties to set, as name → value. Values are written the way Studio's Properties panel shows them: \"12, 0, 5\" for a Vector3, \"0.2, 0.6, 1\" for a Color3, \"Neon\" or \"Enum.Material.Neon\" for an enum, true/false for a bool.",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "tags": {
+    "description": "CollectionService tags to add or remove.",
+    "properties": {
+      "add": {
+        "description": "CollectionService tags to add.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "remove": {
+        "description": "Tags to remove.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  }
+}

addedInput schema / properties / instances / items / required
```
Added value: +[
+  "className"
+]
```
addedInput schema / properties / instances / items / type
```
Added value: +"object"
```

Changed3 schema fields changedv0.3.5Sep 3, 2026

addedInput schema / definitions / __schema0 / properties / attributes / additionalProperties / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "properties": {
+      "type": {
+        "description": "Roblox type to store the attribute as. Needed for anything but a plain string, number or boolean — a bare string stays a string.",
+        "enum": [
+          "string",
+          "boolean",
+          "number",
+          "BrickColor",
+          "CFrame",
+          "Color3",
+          "ColorSequence",
+          "Font",
+          "NumberRange",
+          "NumberSequence",
+          "Rect",
+          "UDim",
+          "UDim2",
+          "Vector2",
+          "Vector3"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "description": "The value, written as the Properties panel shows it: \"0, 5, 0\".",
+        "type": [
+          "string",
+          "number",
+          "boolean"
+        ]
+      }
+    },
+    "required": [
+      "type",
+      "value"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / definitions / __schema0 / properties / attributes / additionalProperties / type
```
Removed value: -[
-  "string",
-  "number",
-  "boolean"
-]
```

changedInput schema / definitions / __schema0 / properties / attributes / description

Previous value: -"Attributes to set, as name → value. An empty string removes one."New value: +"Attributes to set, as name → value. A bare string, number or boolean is stored as-is; for any other type pass { type, value }, e.g. { type: \"Vector3\", value: \"0, 5, 0\" }. An empty string removes an attribute."

Changed4 schema fields changedv0.2.9Aug 30, 2026
- removedInput schema / definitions / __schema0 / properties / attributes / additionalProperties / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
```
- addedInput schema / definitions / __schema0 / properties / attributes / additionalProperties / type
```
Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
```
- removedInput schema / definitions / __schema0 / properties / properties / additionalProperties / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
```
- addedInput schema / definitions / __schema0 / properties / properties / additionalProperties / type
```
Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
```
First observedv0.1.8Aug 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations, the description adds valuable behavioral context: creation happens "as one undoable step," nested builds are "both faster and safer," and property names are validated against the live Roblox API dump before anything is sent to Studio. It also explains why child creation is safer, which helps the agent reason about failure modes. No contradiction with the annotations.

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?

The description is compact and well-structured: one sentence for purpose, one paragraph for nesting strategy, one for API validation, and one for the sibling tool. Every sentence earns its place and no information is redundant with the schema.

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?

For a complex creation tool, the description covers the key operational contexts: nesting, undo behavior, validation, and script-specific routing. The rich schema and annotations handle the parameter-level detail. The only minor gap is that with no output schema, the description does not describe the return value, though for a create operation this may be self-evident from Studio context.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the rationale for `children` (paths are not knowable until existence, same-named siblings make guessing unreliable) and by framing properties/attributes/tags as set-at-creation. It does not repeat parameter syntax, which is already well documented in 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?

The description opens with a specific verb and resource: "Creates instances with their properties, attributes and tags set at creation, as one undoable step." It also differentiates from the closest sibling by saying "Use `script_create` for Script, LocalScript and ModuleScript," so an agent can distinguish this tool from script creation without opening either schema.

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?

The description gives explicit when-to-use guidance: build whole models in one call via `children`, and avoid the separate create-then-address pattern because paths are unknowable until creation. It also names the exact alternative for scripts (`script_create`) and the condition for choosing it. This is concrete, actionable routing guidance.

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

Deploy Server

Create instances

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools