Skip to main content
Glama
EL4CTEO

Roblox Studio MCP

Operate the live game

universe
Destructive

Operate on a published Roblox experience via Open Cloud: restart live servers, message players, manage bans, inspect logs, read analytics, and schedule events.

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.

servers lists the place's live servers — players, uptime, frame rate, memory, version — and logs reads one server's errors and warnings by its jobId, with stack traces and structured-log context. That is where a player's bug report actually happened; Studio only shows your own test. Roblox keeps warnings and errors only, and they arrive about three minutes after they are written.

products lists the game's developer products and game passes with their ids and prices — the ids a purchase script needs. sell creates one, or changes one given itemId. Creating checks the name first, so a retried create cannot leave two "100 Coins" products.

analytics reads the game's own numbers over a date range: players, revenue, retention, crashes, frame rate, as a time series, optionally split by a breakdown such as Platform or Country. Common metrics: DailyActiveUsers, Visits, DailyRevenue, PayingUsers, ForwardD1Retention, AverageSessionLengthMinutes, PeakConcurrentPlayers, ClientCrashCount, ClientFpsP50. Give days for the last N whole UTC days, or startTime and endTime.

events lists the game's scheduled events, or reads one by eventId. schedule creates one (title, startTime, endTime) or changes one given eventId; cancel deletes it. Players see these on the experience's page.

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

Input 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, 'servers' and 'logs' read live servers, 'products' and 'sell' manage products and passes, 'analytics' reads metrics, 'events'/'schedule'/'cancel' manage scheduled events.
daysNoanalytics only: the last N whole UTC days, not counting today. Default 7.
kindNoproducts/sell: 'product' is a developer product (bought again and again: currency, boosts), 'pass' a game pass (bought once: VIP, perks). products lists both when omitted; sell needs it.
nameNosell only: the item's name. Required to create.
imageNosell only: path to a local .png/.jpg/.bmp/.tga icon.
jobIdNologs only: the server, as listed by `servers`.
limitNobans/inventory/servers/logs/events: how many rows to return. analytics: most breakdown series.
priceNosell only: price in Robux.
titleNoschedule only: the event's title.
topicNomessage only: the MessagingService topic.
filterNoinventory: an Open Cloud filter, e.g. `gamePassIds=123` or `assetIds=456`, to ask about specific items rather than listing everything. servers: a CEL filter over the server fields, e.g. `occupancy > 0`. analytics: Dimension=a,b;Dimension=c, e.g. `Platform=Phone,Tablet;Country=US`.
itemIdNosell only: the product or pass to change. Omit to create a new one.
metricNoanalytics only: the metric, e.g. DailyActiveUsers.
searchNologs only: case-insensitive text to find in the message, stack trace or context.
userIdNoban/unban/user/inventory: the player's user id.
confirmNoRequired for restart, message, ban, unban, sell, schedule and cancel. Each of these is visible to players the moment it runs and none can be undone from here.
endTimeNoanalytics/schedule: ISO 8601 UTC end. analytics: exclusive.
eventIdNoevents/schedule/cancel: the event, as listed by `events`.
forSaleNosell only: whether players can buy it. Say it explicitly when creating.
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. servers/logs: which place, defaulting to `cloud place`.
severityNologs only: just this level. Omit for both.
subtitleNoschedule only: a line under the title.
breakdownNoanalytics only: dimensions to split by, e.g. ["Platform"].
startTimeNoanalytics/schedule: ISO 8601 UTC start, e.g. 2026-11-07T18:00:00Z. analytics: inclusive.
universeIdNoWhich game. Omit to use the one set with `cloud universe <id>`.
visibilityNoschedule only: e.g. public.
descriptionNosell/schedule: the item's or event's description.
granularityNoanalytics only: size of each time bucket. Default OneDay. Which a metric allows varies.
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. Changed16 schema fields changedv0.9.1
    • addedInput schema / properties / breakdown
      Added value: +{
      +  "description": "analytics only: dimensions to split by, e.g. [\"Platform\"].",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
    • changedInput schema / properties / confirm / description
      Previous value: -"Required for restart, message, ban, unban and sell. Each of these is visible to players the moment it runs and none can be undone from here."New value: +"Required for restart, message, ban, unban, sell, schedule and cancel. Each of these is visible to players the moment it runs and none can be undone from here."
    • addedInput schema / properties / days
      Added value: +{
      +  "description": "analytics only: the last N whole UTC days, not counting today. Default 7.",
      +  "maximum": 730,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / description / description
      Previous value: -"sell only: the item's description."New value: +"sell/schedule: the item's or event's description."
    • addedInput schema / properties / endTime
      Added value: +{
      +  "description": "analytics/schedule: ISO 8601 UTC end. analytics: exclusive.",
      +  "type": "string"
      +}
    • addedInput schema / properties / eventId
      Added value: +{
      +  "description": "events/schedule/cancel: the event, as listed by `events`.",
      +  "type": "string"
      +}
    • changedInput schema / properties / filter / description
      Previous value: -"inventory: an Open Cloud filter, e.g. `gamePassIds=123` or `assetIds=456`, to ask about specific items rather than listing everything. servers: a CEL filter over the server fields, e.g. `occupancy > 0`."New value: +"inventory: an Open Cloud filter, e.g. `gamePassIds=123` or `assetIds=456`, to ask about specific items rather than listing everything. servers: a CEL filter over the server fields, e.g. `occupancy > 0`. analytics: Dimension=a,b;Dimension=c, e.g. `Platform=Phone,Tablet;Country=US`."
    • addedInput schema / properties / granularity
      Added value: +{
      +  "description": "analytics only: size of each time bucket. Default OneDay. Which a metric allows varies.",
      +  "enum": [
      +    "OneMinute",
      +    "HalfHour",
      +    "OneHour",
      +    "OneDay",
      +    "OneWeek",
      +    "OneMonth",
      +    "None"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"bans/inventory/servers/logs: how many rows to return."New value: +"bans/inventory/servers/logs/events: how many rows to return. analytics: most breakdown series."
    • addedInput schema / properties / metric
      Added value: +{
      +  "description": "analytics only: the metric, e.g. DailyActiveUsers.",
      +  "type": "string"
      +}
    • changedInput schema / properties / op / description
      Previous value: -"'restart' rolls servers onto the new version, 'message' publishes to MessagingService, 'ban'/'unban'/'bans' manage player access, 'user' and 'inventory' look someone up, 'servers' and 'logs' read live servers, 'products' and 'sell' manage products and passes."New value: +"'restart' rolls servers onto the new version, 'message' publishes to MessagingService, 'ban'/'unban'/'bans' manage player access, 'user' and 'inventory' look someone up, 'servers' and 'logs' read live servers, 'products' and 'sell' manage products and passes, 'analytics' reads metrics, 'events'/'schedule'/'cancel' manage scheduled events."
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "restart",
      -  "message",
      -  "ban",
      -  "unban",
      -  "bans",
      -  "user",
      -  "inventory",
      -  "servers",
      -  "logs",
      -  "products",
      -  "sell"
      -]New value: +[
      +  "restart",
      +  "message",
      +  "ban",
      +  "unban",
      +  "bans",
      +  "user",
      +  "inventory",
      +  "servers",
      +  "logs",
      +  "products",
      +  "sell",
      +  "analytics",
      +  "events",
      +  "schedule",
      +  "cancel"
      +]
    • addedInput schema / properties / startTime
      Added value: +{
      +  "description": "analytics/schedule: ISO 8601 UTC start, e.g. 2026-11-07T18:00:00Z. analytics: inclusive.",
      +  "type": "string"
      +}
    • addedInput schema / properties / subtitle
      Added value: +{
      +  "description": "schedule only: a line under the title.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "schedule only: the event's title.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
    • addedInput schema / properties / visibility
      Added value: +{
      +  "description": "schedule only: e.g. public.",
      +  "type": "string"
      +}
  2. Changed16 schema fields changedv0.8.6
    • changedInput schema / properties / confirm / description
      Previous value: -"Required for restart, message, ban and unban. Each of these is visible to players the moment it runs and none can be undone from here."New value: +"Required for restart, message, ban, unban and sell. Each of these is visible to players the moment it runs and none can be undone from here."
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "sell only: the item's description.",
      +  "type": "string"
      +}
    • changedInput schema / properties / filter / description
      Previous value: -"inventory only: an Open Cloud filter, e.g. `gamePassIds=123` or `assetIds=456`, to ask about specific items rather than listing everything."New value: +"inventory: an Open Cloud filter, e.g. `gamePassIds=123` or `assetIds=456`, to ask about specific items rather than listing everything. servers: a CEL filter over the server fields, e.g. `occupancy > 0`."
    • addedInput schema / properties / forSale
      Added value: +{
      +  "description": "sell only: whether players can buy it. Say it explicitly when creating.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / image
      Added value: +{
      +  "description": "sell only: path to a local .png/.jpg/.bmp/.tga icon.",
      +  "type": "string"
      +}
    • addedInput schema / properties / itemId
      Added value: +{
      +  "description": "sell only: the product or pass to change. Omit to create a new one.",
      +  "type": "string"
      +}
    • addedInput schema / properties / jobId
      Added value: +{
      +  "description": "logs only: the server, as listed by `servers`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "products/sell: 'product' is a developer product (bought again and again: currency, boosts), 'pass' a game pass (bought once: VIP, perks). products lists both when omitted; sell needs it.",
      +  "enum": [
      +    "product",
      +    "pass"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"bans/inventory: how many rows to return."New value: +"bans/inventory/servers/logs: how many rows to return."
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "sell only: the item's name. Required to create.",
      +  "type": "string"
      +}
    • changedInput schema / properties / op / description
      Previous value: -"'restart' rolls servers onto the new version, 'message' publishes to MessagingService, 'ban'/'unban'/'bans' manage player access, 'user' and 'inventory' look someone up."New value: +"'restart' rolls servers onto the new version, 'message' publishes to MessagingService, 'ban'/'unban'/'bans' manage player access, 'user' and 'inventory' look someone up, 'servers' and 'logs' read live servers, 'products' and 'sell' manage products and passes."
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "restart",
      -  "message",
      -  "ban",
      -  "unban",
      -  "bans",
      -  "user",
      -  "inventory"
      -]New value: +[
      +  "restart",
      +  "message",
      +  "ban",
      +  "unban",
      +  "bans",
      +  "user",
      +  "inventory",
      +  "servers",
      +  "logs",
      +  "products",
      +  "sell"
      +]
    • changedInput schema / properties / placeId / description
      Previous value: -"ban/unban: restrict to this place only, instead of the whole experience. restart: only restart this place's servers."New value: +"ban/unban: restrict to this place only, instead of the whole experience. restart: only restart this place's servers. servers/logs: which place, defaulting to `cloud place`."
    • addedInput schema / properties / price
      Added value: +{
      +  "description": "sell only: price in Robux.",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "logs only: case-insensitive text to find in the message, stack trace or context.",
      +  "type": "string"
      +}
    • addedInput schema / properties / severity
      Added value: +{
      +  "description": "logs only: just this level. Omit for both.",
      +  "enum": [
      +    "error",
      +    "warning"
      +  ],
      +  "type": "string"
      +}
  3. Addedv0.6.8

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive=true, readOnly=false, openWorld=true, and idempotent=false. The description adds rich behavioral context beyond that: restart bleeds off over 10 minutes by default, message delivery is not confirmed, permanent bans are possible, and logs arrive about three minutes after being written and contain only warnings/errors. No annotation contradiction appears.

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?

Although long, the description is front-loaded with the tool's scope and organized by operation. Each paragraph covers a distinct op or group of ops, and the length is justified by the 15-operation surface area. There is little wasted text relative to the complexity being described.

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 15 operations, 34 parameters, and absence of an output schema, the description is complete enough for correct invocation. It covers prerequisites, destructive-operation confirmation, cross-parameter constraints, and even some return-field context for servers and logs. An agent has sufficient information to select ops and invoke them safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all 34 parameters thoroughly, including parameter-specific details like durationSeconds permanence, bleedOffMinutes defaults, and displayReason/privateReason distinction. The description restates many of these semantics and groups parameters by operation, but it adds little meaning beyond what the schema already provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 by distinguishing live-server operations from Studio work: 'Acts on the PUBLISHED experience and the people in it — not on the place open in Studio.' It then enumerates all 15 operations with concrete scope, so an agent can identify what this tool does without confusion. This clearly differentiates it from Studio-oriented siblings such as inspect, playtest, and execute_luau.

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 operation-specific usage conditions: publishing alone does not update live servers, so use restart; message only reaches servers with a SubscribeAsync listener on the exact topic; bans are permanent without durationSeconds; confirm is required for visible, irreversible operations. It also states the prerequisite: 'Everything here needs an Open Cloud key and a universe id.' This is strong when-to-use and when-not-to-use guidance.

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