Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

mass_create_objects

Generate multiple objects in Roblox Studio simultaneously by specifying class names, parent paths, and optional names. Simplifies bulk object creation for efficient project setup.

Instructions

Create multiple objects at once (basic, without properties)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectsYesArray of objects to create

Implementation Reference

  • The handler function that executes the mass_create_objects tool. Validates the input objects array and forwards the request to the Studio HTTP client endpoint '/api/mass-create-objects', returning the formatted response.
    async massCreateObjects(objects: Array<{className: string, parent: string, name?: string}>) {
      if (!objects || objects.length === 0) {
        throw new Error('Objects array is required for mass_create_objects');
      }
      const response = await this.client.request('/api/mass-create-objects', { objects });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • The input schema definition for the mass_create_objects tool, registered in the MCP server's listTools handler. Defines the expected structure: an array of objects each with className, parent, and optional name.
    {
      name: 'mass_create_objects',
      description: 'Create multiple objects at once (basic, without properties)',
      inputSchema: {
        type: 'object',
        properties: {
          objects: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                className: {
                  type: 'string',
                  description: 'Roblox class name'
                },
                parent: {
                  type: 'string',
                  description: 'Path to the parent instance'
                },
                name: {
                  type: 'string',
                  description: 'Optional name for the object'
                }
              },
              required: ['className', 'parent']
            },
            description: 'Array of objects to create'
          }
        },
        required: ['objects']
      }
  • src/index.ts:690-691 (registration)
    The registration/dispatch case in the MCP server's CallToolRequest handler that routes 'mass_create_objects' calls to this.tools.massCreateObjects.
    case 'mass_create_objects':
      return await this.tools.massCreateObjects((args as any)?.objects);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'basic, without properties' which hints at limitations, but doesn't disclose critical behavioral traits like permissions required, rate limits, whether creation is atomic, error handling for partial failures, or what the tool returns. For a mutation tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence that front-loads the core purpose ('Create multiple objects at once') and adds a crucial qualifier ('basic, without properties'). There is zero wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on return values, error conditions, permissions, and how it differs operationally from similar tools like 'mass_create_objects_with_properties'. The context signals indicate a simple parameter structure, but the behavioral gaps are significant.

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 schema fully documents the 'objects' parameter and its nested structure (className, name, parent). The description adds no additional parameter semantics beyond implying objects are created without properties, which is already suggested by the tool name and description context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Create multiple objects') and resource ('objects'), and distinguishes it from siblings by specifying 'basic, without properties'. However, it doesn't explicitly contrast with 'mass_create_objects_with_properties' beyond the 'without properties' qualifier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for batch creation of simple objects without properties, but doesn't explicitly state when to use this versus 'create_object' (single vs. multiple) or 'mass_create_objects_with_properties' (basic vs. with properties). No guidance on prerequisites or exclusions is provided.

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

Related 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/boshyxd/robloxstudio-mcp'

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