Skip to main content
Glama

gameobject-find

Locate a target GameObject in the open Prefab or active Scene by name, instanceID, or path. Retrieves its details, children, and attached component previews.

Instructions

Finds specific GameObject by provided information in opened Prefab or in a Scene. First it looks for the opened Prefab, if any Prefab is opened it looks only there ignoring a scene. If no opened Prefab it looks into current active scene. Returns GameObject information and its children. Also, it returns Components preview just for the target GameObject.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameObjectRefYesGameObject reference. SCHEMA: {"name":"Main Camera"} or {"instanceID":12345} or {"path":"Canvas/Panel/Button"}
includeDataNoInclude editable GameObject data (tag, layer, etc).false
includeComponentsNoInclude attached components references.false
includeBoundsNoInclude 3D bounds of the GameObject.false
includeHierarchyNoInclude hierarchy metadata.false
hierarchyDepthNoDetermines the depth of the hierarchy to include. 0 - means only the target GameObject. 1 - means to include one layer below.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses search order, return content (GameObject info, children, components preview), but does not explicitly state read-only behavior or error handling. The behavioral details are adequate but not exhaustive.

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 concise (4 sentences) with no wasted words. Each sentence adds value: search context, precedence, return values. It is front-loaded and to the point.

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

Completeness3/5

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

Given 6 parameters, no output schema, and no annotations, the description explains search behavior but lacks details on missing objects, error responses, or output format. It is moderately complete but leaves gaps.

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 coverage is 100% (6 parameters, all described). The description adds minimal extra meaning beyond schema descriptions. For example, it says 'returns components preview' which relates to includeComponents, but does not clarify interactions like hierarchyDepth depending on includeHierarchy.

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?

The description uses a specific verb ('Finds') and resource ('GameObject'), and clearly distinguishes the search context (opened Prefab vs Scene). It differentiates from sibling tools like gameobject-create or gameobject-destroy by focusing on finding and returning information.

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

Usage Guidelines4/5

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

The description explains when to use the tool (to find a GameObject in a prefab or scene) and states the search precedence (prefab first, then scene). It does not explicitly mention alternatives or when not to use it, but the context is clear enough for an agent to decide.

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

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/butterlatte-zhang/unity-ai-bridge'

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