Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

get_instance_children

Retrieve child objects and their types from a specified parent instance in Roblox Studio, enabling efficient navigation and interaction with project structures.

Instructions

Get child objects and their types

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instancePathYesPath to the parent instance

Implementation Reference

  • The core implementation of the get_instance_children tool handler. It validates the instancePath input, makes an HTTP request to the Studio bridge for instance children data, and returns a formatted MCP response with the JSON data.
    async getInstanceChildren(instancePath: string) {
      if (!instancePath) {
        throw new Error('Instance path is required for get_instance_children');
      }
      const response = await this.client.request('/api/instance-children', { instancePath });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • src/index.ts:154-167 (registration)
    MCP tool registration entry defining the name, description, and input schema for get_instance_children. This is returned by the listTools MCP method.
    {
      name: 'get_instance_children',
      description: 'Get child objects and their types',
      inputSchema: {
        type: 'object',
        properties: {
          instancePath: {
            type: 'string',
            description: 'Path to the parent instance'
          }
        },
        required: ['instancePath']
      }
    },
  • src/index.ts:664-665 (registration)
    Dispatch handler in the MCP CallToolRequestSchema that routes calls to the getInstanceChildren tool method based on the tool name.
    case 'get_instance_children':
      return await this.tools.getInstanceChildren((args as any)?.instancePath as string);
  • HTTP proxy endpoint that exposes the get_instance_children tool via POST /mcp/get_instance_children for direct HTTP calls from the Studio plugin or other clients.
    app.post('/mcp/get_instance_children', async (req, res) => {
      try {
        const result = await tools.getInstanceChildren(req.body.instancePath);
        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?

No annotations are provided, so the description carries full burden. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't disclose behavioral traits such as permissions needed, rate limits, error handling, or what 'child objects' entails (e.g., depth, format). This leaves significant gaps for a tool with no annotation coverage.

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 with no wasted words. It's front-loaded with the core action and target, making it easy to parse quickly. Every word earns its place, achieving optimal conciseness for the information provided.

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?

Given no annotations, no output schema, and a vague description, the tool's context is incomplete. The description doesn't clarify what 'child objects' are, how results are structured, or any limitations, making it inadequate for a tool that likely returns complex data. More detail is needed to compensate for the lack of structured fields.

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%, with the single parameter 'instancePath' documented as 'Path to the parent instance'. The description adds no meaning beyond this, as it doesn't explain the parameter's role or format. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles parameter documentation adequately.

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

Purpose3/5

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

The description 'Get child objects and their types' clearly states the action (get) and target (child objects and types), but it's vague about what 'objects' and 'types' refer to in this context. It doesn't distinguish this tool from siblings like 'get_instance_properties' or 'get_project_structure', leaving ambiguity about scope and resource specificity.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_instance_properties' and 'get_project_structure' that might overlap in functionality, the description lacks context on prerequisites, exclusions, or comparisons, offering no help for tool selection.

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