Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

create_object_with_properties

Generate and configure Roblox objects with specific properties in Roblox Studio, defining class, parent, name, and attributes directly upon creation.

Instructions

Create a new Roblox object instance with initial properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
classNameYesRoblox class name (e.g., "Part", "Script", "Folder")
nameNoOptional name for the new object
parentYesPath to the parent instance (e.g., "game.Workspace")
propertiesNoProperties to set on creation

Implementation Reference

  • The primary handler function that implements the create_object_with_properties tool logic by proxying a creation request (with properties) to the Roblox Studio bridge service via HTTP API.
    async createObjectWithProperties(className: string, parent: string, name?: string, properties?: Record<string, any>) {
      if (!className || !parent) {
        throw new Error('Class name and parent are required for create_object_with_properties');
      }
      const response = await this.client.request('/api/create-object', { 
        className, 
        parent, 
        name, 
        properties 
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • The input schema defining parameters, types, descriptions, and required fields for the create_object_with_properties tool.
    inputSchema: {
      type: 'object',
      properties: {
        className: {
          type: 'string',
          description: 'Roblox class name (e.g., "Part", "Script", "Folder")'
        },
        parent: {
          type: 'string',
          description: 'Path to the parent instance (e.g., "game.Workspace")'
        },
        name: {
          type: 'string',
          description: 'Optional name for the new object'
        },
        properties: {
          type: 'object',
          description: 'Properties to set on creation'
        }
      },
      required: ['className', 'parent']
    }
  • src/index.ts:688-689 (registration)
    Registration and dispatch of the create_object_with_properties tool in the MCP CallToolRequest handler switch statement.
    case 'create_object_with_properties':
      return await this.tools.createObjectWithProperties((args as any)?.className as string, (args as any)?.parent as string, (args as any)?.name, (args as any)?.properties);
  • src/index.ts:311-312 (registration)
    Tool registration in the MCP ListToolsRequest response, including name, description, and reference to schema.
    {
      name: 'create_object_with_properties',
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 states this is a creation operation but doesn't mention permissions required, whether it's idempotent, error handling, or what happens if properties conflict. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded with the core functionality.

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 insufficient. It doesn't explain what happens on success (e.g., returns the created object ID), error conditions, or behavioral constraints. Given the complexity of creating objects with properties in Roblox, more context 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 already documents all four parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'initial properties' which aligns with the 'properties' parameter, but doesn't provide additional context about property formats or constraints.

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') and resource ('new Roblox object instance'), specifying it's for creating objects with initial properties. It distinguishes from the simpler 'create_object' sibling by mentioning 'with initial properties', though it doesn't explicitly contrast with 'mass_create_objects_with_properties'.

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 'create_object' (without properties) or 'mass_create_objects_with_properties' (for bulk operations). It mentions 'with initial properties' but doesn't clarify the trade-offs or appropriate contexts for choosing this specific tool.

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