Skip to main content
Glama
EL4CTEO

Roblox Studio MCP

by EL4CTEO
OverviewSchemaRelated ServersScoreDiscussions
Local

Create instances

create
Destructive

Build Roblox instances with properties, attributes, and tags in one undoable step. Nest children to construct entire models in a single call, with property names validated against the live API.

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
NameRequiredDescriptionDefault
studioIdNoTarget Studio; omit for the active one.
instancesYesInstances to create together as one undoable step.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.3.5
    • 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."
  2. Changed4 schema fields changedv0.2.9
    • 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"
+]
  3. First observedv0.1.8

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that creation is a single undoable step, that property names are validated against the live Roblox API dump before transmission, and that typos return closest real names instead of engine errors. It also warns that an instance's path is unknowable until it exists and that same-named siblings make guessing unreliable. These are meaningful behavioral details not present in 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 four tight sentences with no filler. The core purpose is front-loaded in the first sentence, followed by nested usage rationale, validation behavior, and a sibling-routing instruction. Every sentence earns its place.

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?

Given the rich input schema, relevant annotations, and the absence of an output schema, the description covers what the agent needs: what the tool does, when to use an alternative, how to structure complex creates, and how errors are surfaced. Nothing critical for correct invocation is missing.

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?

The input schema already provides 100% coverage with detailed parameter descriptions, so the baseline is 3. The description adds extra semantic value by explaining why children should be used for building models and how property validation handles typo'd names. It does not duplicate schema content but enhances conceptual understanding of parameters.

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 clearly differentiates from the sibling by explicitly directing Script, LocalScript, and ModuleScript creation to script_create. The purpose is unambiguous and not a tautology.

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: 'Use script_create for Script, LocalScript and ModuleScript — it takes source directly.' It also explains when nesting children is preferable and why, addressing the reliability of addressing newly created instances. This provides strong decision support for selecting between alternatives.

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/EL4CTEO/rbx-studio-mcp'

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