Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx

Create a new Instance in the live game

create-instance
Destructive

Creates a new Roblox Instance, sets optional Name/properties, and parents it to a path to spawn parts, GUIs, folders, or value objects for live debugging.

Instructions

WRITES LIVE GAME STATE. Construct a brand-new Instance via Instance.new(className), optionally set its Name and a list of initial properties, and optionally parent it into the game tree. Useful while debugging for spawning a Part, a Highlight/BillboardGui ESP marker, a Folder, a Value object (IntValue/StringValue/BoolValue), or any other class. PROCESS: Instance.new is pcall-guarded (returns a clean error if className is invalid); Name is set if provided; each property is set independently and pcall-guarded so one bad property does not abort the others (failures are collected into propErrors); Parent is set LAST (only if parentPath is given) so all properties are applied before the instance becomes live in the tree. If you do NOT pass parentPath the instance is created but left parentless (nil) — it still exists in memory and can be parented later via set-instance-property on its Parent. WARNING: a parented instance immediately affects the running game and may replicate. Returns { Created, ClassName, Parented, propErrors, ok } or { error }. Signature: { className: string, name: string?, parentPath: string?, properties: {{ name: string, value: { kind: "string" | "number" | "boolean" | "nil" | "raw", value: string | number | boolean? } }}?, threadContext: number? }. Phase: act; cost=medium; idempotency=contextual-write. Requires: active-client, resolved-target, explicit-mutation-approval. Produces: created-handle. Verify with: get-instance-properties. Safety: MUTATING; writes live game/client state. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional Name to assign to the new instance. If omitted the engine's default name for the class is kept.
classNameYesThe Roblox class name to instantiate, e.g. 'Part', 'Folder', 'Highlight', 'BillboardGui', 'IntValue', 'StringValue', 'ScreenGui'. Passed to Instance.new(className); an unknown/non-creatable class returns a clean error.
parentPathNoOptional Luau expression resolving to the Instance that should become the new instance's Parent, e.g. 'game.Workspace', 'game.Players.LocalPlayer.PlayerGui', or 'game:GetService("ReplicatedStorage")'. Evaluated as `return <parentPath>`. Set LAST, after all properties. Omit to leave the instance parentless.
propertiesNoOptional list of initial properties to assign before parenting, e.g. [{ name: 'Anchored', value: { kind: 'boolean', value: true } }, { name: 'Size', value: { kind: 'raw', value: 'Vector3.new(4,1,4)' } }]. Omit or pass [] for none.
threadContextNoOptional Roblox thread identity for this call; omit it to use the server default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-spies.2

TDQS

A4.6/5.0
Behavior5/5

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

With annotations already declaring destructive=true and non-idempotent, the description goes well beyond: pcall-guarded className validation, per-property pcall isolation collecting propErrors, Parent applied LAST, parentless-by-default behavior, and the replication warning. This is rich behavioral context an agent cannot derive from structured fields.

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 live-state warning is correctly front-loaded and the PROCESS paragraph is dense with useful detail. The embedded 'Signature:' line and phase/cost/idempotency meta largely restate schema and annotations, which is minor waste.

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?

No output schema exists, but the description documents the return shape ({ Created, ClassName, Parented, propErrors, ok } or { error }), failure handling, and a verification step. An agent has everything needed to invoke and interpret results.

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%, giving a baseline of 3, but the description adds ordering semantics beyond per-parameter docs — properties are applied before Parent, and parentPath is evaluated as a Luau expression. The duplicated signature line is redundant but the process detail adds real meaning.

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+resource: 'Construct a brand-new Instance via Instance.new(className)' with optional Name, properties, and parenting. It is distinguishable from siblings like clone-instance, set-instance-property, and destroy-instance by its creation semantics.

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?

Explains when to use it with concrete debugging examples (Part, ESP marker, Folder, Value objects) and lists prerequisites (active-client, resolved-target, explicit-mutation-approval) plus a verification tool. It does not explicitly contrast with clone-instance for existing instances, leaving some alternative selection to inference.

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

Deploy Server

Other Tools