Skip to main content
Glama
AnkleBreaker-Studio

Unity MCP Server

by AnkleBreaker-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unity_build

Build a Unity project for a selected target platform and output path, with optional scenes and development settings.

Instructions

Build the project for a target platform.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoUnity instance port (from unity_select_instance). Always include it when multiple instances run.
scenesNoScene paths; default: enabled Build Settings scenes
targetYesPlatform
outputPathYesBuild output path
developmentBuildNoDevelopment build (default: false)
managedCodeVariantNoUnity 6.6+, protocol 3. Default: Checked for Development, Release otherwise. This build only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.36.0
    • changedInput schema / properties / developmentBuild / description
      Previous value: -"Enable development build (default: false)"New value: +"Development build (default: false)"
    • addedInput schema / properties / managedCodeVariant
      Added value: +{
+  "description": "Unity 6.6+, protocol 3. Default: Checked for Development, Release otherwise. This build only.",
+  "enum": [
+    "Release",
+    "Instrumented",
+    "Checked",
+    "Debug"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / outputPath / description
      Previous value: -"Output path for the build"New value: +"Build output path"
    • changedInput schema / properties / scenes / description
      Previous value: -"Scene paths to include (default: scenes in build settings)"New value: +"Scene paths; default: enabled Build Settings scenes"
    • changedInput schema / properties / target / description
      Previous value: -"Build target platform"New value: +"Platform"
  2. Changed1 schema field changedv2.35.6
    • changedInput schema / properties / port / description
      Previous value: -"Target Unity instance port for parallel-safe routing. Get this from unity_select_instance. When working with multiple Unity instances, ALWAYS include this parameter."New value: +"Unity instance port (from unity_select_instance). Always include it when multiple instances run."
  3. Addedv2.28.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations, so the description carries the full burden, and it says nothing about this being a long-running, mutating operation that writes to disk, may overwrite an existing output path, or blocks the editor. The schema hints that multiple instances require a port, but the description does not surface that constraint or any failure semantics.

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?

A single front-loaded sentence with zero filler. It is efficient, though at the cost of leaving the definition under-specified rather than over-written.

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 6-parameter destructive/mutating build operation with no annotations and no output schema, one sentence is not enough. Nothing tells the agent whether the build is synchronous, what a successful versus failed build looks like, or whether the editor remains usable afterward.

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% and includes enums and defaults, so parameters are already fully documented. The description adds no additional meaning (no notes on outputPath overwrite behavior or how scenes interact with Build Settings). Baseline 3 is correct.

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?

Clear verb+resource+scope: 'Build the project for a target platform.' No sibling performs builds, so distinction is implicit but the description never names the workflow it belongs to (instance selection, play mode, etc.). Understandable on its own, but thin.

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 on when to build, prerequisites (e.g. that a Unity instance must be selected/running, that compilation errors should be checked first), or how it relates to unity_play_mode or unity_get_compilation_errors. The agent must infer all context.

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