roblox-devproducts-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBLOX_API_KEY | No | Your Roblox Open Cloud API key (used as fallback if not stored via the setup command) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_developer_productsA | List the developer products for a Roblox universe (game). Returns each item's ID, name, price, description, and on-sale status. Use this to see a game's developer products or to find an ID before updating one. |
| get_developer_productA | Get the full details of a single developer product by its ID within a universe. |
| create_developer_productA | Create a new developer product in a universe. Only a name is required. To make it purchasable, also pass priceInRobux and isForSale: true — it cannot be put on sale without a price. Returns the created developer product including its new ID. Requires an API key scoped to write developer products. |
| update_developer_productA | Update an existing developer product's name, description, price, or on-sale status. Only the fields you provide change. Putting it on sale (isForSale: true) requires a price. Returns the updated developer product. Requires an API key scoped to write developer products. |
| bulk_create_developer_productsA | Create many developer products in one call. Use this instead of calling create_developer_product repeatedly. Items are created sequentially with automatic rate limiting (the API allows 3 writes/second). Returns a summary plus a per-item result (created 'id' or error); one failing item does not stop the rest. |
| bulk_update_developer_productsA | Update many developer products in one call. Use this instead of calling update_developer_product repeatedly. Each entry targets one by ID and changes only the fields you provide. Items are updated sequentially with automatic rate limiting (3 writes/second). Returns a summary plus a per-item result; one failing item does not stop the rest. |
| list_game_passesA | List the game passes for a Roblox universe (game). Returns each item's ID, name, price, description, and on-sale status. Use this to see a game's game passes or to find an ID before updating one. |
| get_game_passA | Get the full details of a single game pass by its ID within a universe. |
| create_game_passA | Create a new game pass in a universe. Only a name is required. To make it purchasable, also pass priceInRobux and isForSale: true — it cannot be put on sale without a price. Returns the created game pass including its new ID. Requires an API key scoped to write game passes. |
| update_game_passA | Update an existing game pass's name, description, price, or on-sale status. Only the fields you provide change. Putting it on sale (isForSale: true) requires a price. Returns the updated game pass. Requires an API key scoped to write game passes. |
| bulk_create_game_passesA | Create many game passes in one call. Use this instead of calling create_game_pass repeatedly. Items are created sequentially with automatic rate limiting (the API allows 5 writes/second). Returns a summary plus a per-item result (created 'id' or error); one failing item does not stop the rest. |
| bulk_update_game_passesA | Update many game passes in one call. Use this instead of calling update_game_pass repeatedly. Each entry targets one by ID and changes only the fields you provide. Items are updated sequentially with automatic rate limiting (5 writes/second). Returns a summary plus a per-item result; one failing item does not stop the rest. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool maps to a distinct combination of resource type (developer product vs. game pass) and action (get, list, create, update, bulk create, bulk update), with no overlapping purposes. The bulk variants are clearly distinguished from their single-item counterparts by name and description.
All tool names follow the exact same verb_noun pattern: get_, list_, create_, update_, bulk_create_, and bulk_update_ are each paired with either developer_products or game_passes. Naming is uniform, predictable, and easy to navigate.
Twelve tools is well-scoped for a server covering two closely related Roblox monetization resources. Each resource gets the same complete set of six operations, so no tool feels redundant or unnecessary.
The surface covers read (get/list), create, update, and bulk operations for both resource types, but notably lacks delete operations for either developer products or game passes. This is a minor gap since the core purchase/lifecycle workflows are well represented, but deletion is an obvious missing CRUD action.