Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

mass_create_objects_with_properties

Batch-create multiple Roblox objects with specific properties and parent instances in Roblox Studio using this MCP server tool, streamlining game development workflows.

Instructions

Create multiple objects at once with initial properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectsYesArray of objects to create with properties

Implementation Reference

  • The core handler function that validates the input and forwards the mass creation request to the Roblox Studio bridge API endpoint '/api/mass-create-objects-with-properties'.
    async massCreateObjectsWithProperties(objects: Array<{className: string, parent: string, name?: string, properties?: Record<string, any>}>) {
      if (!objects || objects.length === 0) {
        throw new Error('Objects array is required for mass_create_objects_with_properties');
      }
      const response = await this.client.request('/api/mass-create-objects-with-properties', { objects });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • MCP tool registration including detailed input schema defining the expected structure for the 'objects' array with className, parent, optional name and properties.
      name: 'mass_create_objects_with_properties',
      description: 'Create multiple objects at once with initial 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'
                },
                properties: {
                  type: 'object',
                  description: 'Properties to set on creation'
                }
              },
              required: ['className', 'parent']
            },
            description: 'Array of objects to create with properties'
          }
        },
        required: ['objects']
      }
    },
  • src/index.ts:692-693 (registration)
    Dispatch registration in the MCP CallToolRequestSchema handler that routes calls to the tools handler function.
    case 'mass_create_objects_with_properties':
      return await this.tools.massCreateObjectsWithProperties((args as any)?.objects);
  • HTTP proxy endpoint for direct HTTP calls to the tool from the Studio plugin bridge.
    app.post('/mcp/mass_create_objects_with_properties', async (req, res) => {
      try {
        const result = await tools.massCreateObjectsWithProperties(req.body.objects);
        res.json(result);
      } catch (error) {
        res.status(500).json({ error: error instanceof Error ? error.message : 'Unknown error' });
      }
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions creation and property setting but omits critical details: whether this requires specific permissions, how errors are handled (e.g., partial failures), rate limits, or what the response looks like (e.g., returns IDs). For a batch mutation tool, this is a significant gap.

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 functionality ('Create multiple objects at once') and adds the key qualifier ('with initial properties'). There's no wasted verbiage or redundancy.

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 batch creation tool with no annotations and no output schema, the description is inadequate. It doesn't address error handling, response format, permissions, or performance implications. Given the complexity of batch operations and the lack of structured data, more contextual guidance is needed.

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. The description adds minimal value by implying batch creation and property initialization, but doesn't clarify semantics beyond what the schema provides (e.g., what 'initial properties' means contextually).

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 action ('Create multiple objects at once') and the key feature ('with initial properties'), which distinguishes it from basic creation tools. However, it doesn't explicitly differentiate from sibling tools like 'mass_create_objects' or 'create_object_with_properties' beyond the 'multiple objects' aspect.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'mass_create_objects' (which might not set properties) or 'create_object_with_properties' (which creates single objects). There's no mention of prerequisites, performance considerations, or trade-offs for batch creation.

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