Skip to main content
Glama
EL4CTEO

Roblox Studio MCP

by EL4CTEO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Browse hierarchy

tree
Read-onlyIdempotent

Lists the instance hierarchy under a path in Roblox Studio as a flat array of paths, helping you orient in unfamiliar projects.

Instructions

Lists the instance hierarchy under a path, breadth-first to a given depth. Returns a flat array of paths — flat is both cheaper and easier to act on than nested JSON, since every entry is directly usable as a path.

Use this to orient yourself in an unfamiliar place. Use find instead when you already know what you are looking for; a deep tree over a whole place wastes context on instances you will never touch.

With path omitted it lists only the containers a place is authored in — Workspace, ReplicatedStorage, ServerScriptService and friends. Roblox exposes ~120 services at the root, almost all engine internals; those are hidden and the response says how many. Pass an explicit path to look inside one of them anyway.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoDot-notation root, e.g. "Workspace.Map". Omit to list services from the root.
depthNoLevels below `path` to walk. Keep low; each level multiplies the result.
limitNoMaximum items to return (1-500).
cursorNoOpaque cursor from a previous call's `nextCursor`. Omit for the first page.
detailNoconcise: compact identity. standard: selected facts. full: all readable properties for inspect; tree/find use the same columns as standard.standard
studioIdNoTarget Studio; omit for the active one.
classNameNoOnly include instances of this class or a subclass, e.g. "BasePart".
nameContainsNoOnly include instances whose name contains this text (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.6
    • changedInput schema / properties / detail / description
      Previous value: -"How much to return per item. 'concise' = name + class only, cheapest, use when scanning or counting. 'standard' = the properties that matter for most edits. 'full' = every readable property, expensive — use only after you have narrowed to a handful of instances."New value: +"concise: compact identity. standard: selected facts. full: all readable properties for inspect; tree/find use the same columns as standard."
  2. First observedv0.1.8

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the flat-array return format, the depth-multiplication cost warning, and the fact that ~120 engine-internal root services are hidden with a count reported. It stops short of covering pagination/error behavior, but that is a minor omission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core behavior, then guidance, then the omit-path edge case — a sensible progression. Three paragraphs is slightly long, and the 'flat is both cheaper and easier to act on' rationale is arguably more justification than an agent needs, but every sentence carries information.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing the return value, and it does (flat array of paths, hidden-service count). Combined with the sibling routing and the omit-path explanation, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema itself documents all 8 parameters including the omitted-path behavior. The description still adds value on `path` (what the omitted case actually yields and why services are hidden) and on `depth` (cost implication), going modestly beyond the schema's own text.

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

Purpose5/5

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

States a specific verb and resource: 'Lists the instance hierarchy under a path, breadth-first to a given depth.' It also states the return shape (flat array of paths) and explicitly distinguishes itself from the sibling `find`, so an agent can select it without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('orient yourself in an unfamiliar place') and when-not ('Use `find` instead when you already know what you are looking for'), plus the cost rationale for avoiding deep trees. It also explains the omit-path case, which selects a materially different behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools