Skip to main content
Glama
AnkleBreaker-Studio

Unity MCP Server

by AnkleBreaker-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unity_screenshot_editor_window

Capture a Unity EditorWindow to PNG without requesting keyboard focus. Use only on explicit user request; hidden tabs need activateTab and ambiguous names return id: options.

Instructions

Capture an existing EditorWindow to PNG (Windows PrintWindow) without requesting keyboard focus. Hidden tabs require activateTab:true; ambiguous names return id: candidates. GPU/minimized windows can refuse capture. USE ONLY ON EXPLICIT USER REQUEST; never proactively or for your own inspection. On macOS/Linux report unsupported, do not retry; use Game/Scene captures there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoSave path ending in .png (default: Assets/Screenshots/EditorWindow_<time>.png).
portNoUnity instance port (from unity_select_instance). Always include it when multiple instances run.
windowYesFull type name, simple name, tab title, or id: selector from candidates.
activateTabNoTemporarily select an existing tab, then restore its predecessor (default false; newer plugins). Does not request keyboard focus.
maxDimensionNoMax side (default 8192, clamped to GPU). Full window and crop each limited to 33554432 pixels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.36.0
    • addedInput schema / properties / activateTab
      Added value: +{
+  "description": "Temporarily select an existing tab, then restore its predecessor (default false; newer plugins). Does not request keyboard focus.",
+  "type": "boolean"
+}
    • changedInput schema / properties / maxDimension / description
      Previous value: -"Max pixels per side (default 8192, clamped to GPU max)."New value: +"Max side (default 8192, clamped to GPU). Full window and crop each limited to 33554432 pixels."
    • changedInput schema / properties / window / description
      Previous value: -"EditorWindow type FullName (e.g. 'UnityEditor.InspectorWindow'), simple type name, or tab title."New value: +"Full type name, simple name, tab title, or id: selector from candidates."
  2. Addedv2.35.6

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses platform limits (Windows-only, unsupported on macOS/Linux, do not retry), failure modes (GPU/minimized windows may refuse), focus behavior (no keyboard focus), and the ambiguous-name/id: fallback. This is rich behavioral context an agent needs.

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 action and dense with useful facts; every sentence carries information (platform fallback, activation rule, failure mode, usage constraint). Slightly telegraphic, but no wasted sentences.

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?

For a screenshot tool with no output schema and no annotations, the description covers mechanism, platform support, error/refusal behavior, activation semantics, and usage constraints thoroughly. An agent has everything needed to call it correctly or decline to.

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 already documents all five parameters (baseline 3). The description adds cross-parameter meaning beyond the schema by linking hidden tabs to activateTab:true and ambiguous names to id: candidates, which helps the agent wire parameters correctly.

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 (Capture), resource (EditorWindow), output format (PNG), and mechanism (Windows PrintWindow). It clearly distinguishes itself from the sibling scene/game capture tools, which it explicitly names as alternatives.

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 (ONLY on explicit user request), when-not (never proactively or for self-inspection), and the alternative on other platforms ('use Game/Scene captures there'). No inference required.

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