Skip to main content
Glama

prefab

Manage Unity prefabs: create variants, apply or revert overrides, instantiate, and inspect prefab status.

Instructions

Advanced Unity prefab operations. Actions:

  • get_info: Get prefab status (instance/asset type, variant, overrides)

  • create_variant: Create a prefab variant from a base prefab

  • get_overrides: List property modifications, added/removed components

  • apply_overrides: Apply all instance overrides back to the prefab asset

  • revert_overrides: Revert all instance overrides

  • unpack: Unpack a prefab instance (outermost or completely)

  • open: Open prefab in prefab editing mode

  • close: Close prefab editing mode, return to main stage

  • instantiate: Instantiate a prefab into the scene with optional position/parent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesPrefab action to perform
objectIdNoInstance ID of a prefab instance
positionNoJSON position object for instantiate, e.g. {"x":0,"y":1,"z":0}
assetPathNoPath to the prefab asset (e.g. Assets/Prefabs/Player.prefab)
completelyNoFor unpack: "true" to unpack completely, "false" for outermost only
objectPathNoHierarchy path of a prefab instance in the scene
parentPathNoHierarchy path of parent for instantiate
variantPathNoDestination path for create_variant
Behavior3/5

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

The description names actions like 'apply_overrides' and 'revert_overrides', which imply mutability, but does not elaborate on side effects, permissions, or destructive potential beyond the annotation 'readOnlyHint: false'.

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 and front-loaded with a clear list of actions. Every sentence serves a purpose with no unnecessary text.

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 the tool's complexity with 9 actions and 8 parameters, the description lacks essential mapping of required parameters per action, leaving the agent without enough context to correctly invoke sub-actions.

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?

The input schema has 100% coverage with descriptions for each parameter, so the tool description adds no additional meaning. The description merely lists actions without linking parameters to specific actions.

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 clearly states 'Advanced Unity prefab operations' and lists 9 specific actions, effectively communicating the tool's purpose and distinguishing it from sibling tools like 'create_prefab' which focuses on creation.

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 explicit guidance on when to use this tool versus alternatives is provided. The description lists actions but does not compare with siblings such as 'create_prefab' or 'update_gameobject', leaving the agent to infer usage.

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/joel-wehr/unity-mcp'

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