Skip to main content
Glama
EL4CTEO

Roblox Studio MCP

by EL4CTEO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Operate the live game

universe
Destructive

Manage a published Roblox experience live: restart servers, message all servers, ban/unban players, and look up users or inventory.

Instructions

Acts on the PUBLISHED experience and the people in it — not on the place open in Studio.

restart rolls live servers onto the version you just published. Publishing on its own changes nothing for anyone already playing: they stay on their server, running the old code, until it empties. This is the step people forget. By default it bleeds off over 10 minutes — matchmaking stops and players finish what they are doing — rather than shutting servers down under them, which is what Roblox's own default does.

message publishes to MessagingService, reaching every live server at once. Only servers with a SubscribeAsync listener on that exact topic receive it, and nothing reports whether anything was listening, so success here does not mean delivery.

ban and unban set a player's game-join restriction. A ban with no durationSeconds is PERMANENT. displayReason is shown to the player; privateReason is for your records. Scope it to one place with placeId, or leave that out to cover the whole experience. bans lists who is currently restricted.

user looks up a user id — the name-to-id step most other calls need. inventory reports what someone owns: passes, badges, assets.

Everything here needs an Open Cloud key and a universe id. The user sets both once with cloud in the Studio panel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYes'restart' rolls servers onto the new version, 'message' publishes to MessagingService, 'ban'/'unban'/'bans' manage player access, 'user' and 'inventory' look someone up.
limitNobans/inventory: how many rows to return.
topicNomessage only: the MessagingService topic.
filterNoinventory only: an Open Cloud filter, e.g. `gamePassIds=123` or `assetIds=456`, to ask about specific items rather than listing everything.
userIdNoban/unban/user/inventory: the player's user id.
confirmNoRequired for restart, message, ban and unban. Each of these is visible to players the moment it runs and none can be undone from here.
messageNomessage only: the payload, as a string.
placeIdNoban/unban: restrict to this place only, instead of the whole experience. restart: only restart this place's servers.
universeIdNoWhich game. Omit to use the one set with `cloud universe <id>`.
displayReasonNoban only: shown to the player when they are turned away.
privateReasonNoban only: your own record. The player never sees it.
bleedOffMinutesNorestart only: minutes to let existing servers drain. 0 shuts them down immediately, moving players mid-game. Defaults to 10.
durationSecondsNoban only: how long, in seconds. OMIT THIS AND THE BAN IS PERMANENT — say so to the user before you do it.
excludeAltAccountsNoban only: if true, the ban applies to this account alone rather than to alts Roblox links to it. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.8

TDQS

A4.6/5.0
Behavior5/5

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

The description adds significant behavioral detail beyond annotations: restart bleeds off over 10 minutes rather than Roblox's default hard shutdown, message delivery is unacknowledged, bans without durationSeconds are permanent, and confirm is required because 'none can be undone from here.' This fully complements the destructiveHint and openWorldHint 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 organized by operation with a front-loaded key contrast, then per-op explanations, then shared auth context. It is long because the tool has 14 parameters and 7 operations, but every sentence contributes actionable information without padding.

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?

It covers auth setup, per-operation caveats, and rough return meanings for bans, user, and inventory. There is no output schema, and the description does not state precise response shapes for restart, message, ban, or unban, but an agent has enough context to invoke the tool correctly and interpret basic outcomes.

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. The description adds useful extra semantics: userId is 'the name-to-id step most other calls need,' bans scope via placeId, and inventory reports passes/badges/assets. It does not repeat every schema detail, but it adds meaning beyond the structured fields.

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 precise scope: 'Acts on the PUBLISHED experience and the people in it — not on the place open in Studio.' It then enumerates each operation with a distinct verb and target, so an agent can tell what the tool does and how it differs from Studio-side tools.

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?

It gives concrete when-to-use guidance, especially for restart ('This is the step people forget') and message ('success here does not mean delivery'). It also states the auth prerequisite. It does not systematically name sibling alternatives or explicit when-not-to-use conditions, but the context is strong enough for operation selection.

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