Skip to main content
Glama

unity_screenshot_editor_window

Capture an occluded Unity Editor window (Inspector, Project, Console) to a PNG file without stealing focus. Works on Windows only.

Instructions

Capture a specific Editor window (Inspector, Project, Console, custom) to a PNG file via Win32 PrintWindow — works even when occluded, no focus steal. USE ONLY ON EXPLICIT USER REQUEST — never proactively or for your own inspection. WINDOWS EDITOR ONLY: on macOS/Linux it returns { success:false, platform } — do not retry, tell the user it's unavailable there. For game/scene views use unity_screenshot_game / unity_screenshot_scene (cross-platform).

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.
windowYesEditorWindow type FullName (e.g. 'UnityEditor.InspectorWindow'), simple type name, or tab title.
maxDimensionNoMax pixels per side (default 8192, clamped to GPU max).
Behavior4/5

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

Discloses platform constraint, underlying method (Win32 PrintWindow), and behavior when occluded. No annotations provided, so description carries burden. Lacks details on permissions or side effects but sufficient for screenshot tool.

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?

Concise, front-loaded with key action, then usage restrictions and alternatives. Every sentence adds value; no waste.

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 4 parameters, no output schema, no annotations, the description fully addresses purpose, constraints, platform, and sibling differentiation. Complete for agent decision-making.

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 covers all 4 parameters with descriptions (100% coverage). Description does not add extra semantics beyond schema. Baseline 3 appropriate.

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?

Clearly states the tool captures a Unity Editor window to PNG using Win32 PrintWindow, with specific details like working when occluded and no focus steal. Explicitly distinguishes from siblings for game/scene screenshots.

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?

Clearly states to use only on explicit user request, not proactively. Explains Windows-only limitation and tells agent to inform user on other platforms. Points to cross-platform alternatives.

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/AnkleBreaker-Studio/unity-mcp-server'

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