Skip to main content
Glama
Sign In
unity-profiler-mcp

unity-profiler-mcp

by shin0112
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

profiler_export

Loads a saved Unity Profiler capture in the open Editor and exports per-marker main-thread statistics to .data.markers.json for marker-level analysis. Large captures can block the Editor.

Instructions

Have the open Unity Editor load a capture and export per-marker main-thread statistics to .data.markers.json. Large captures can take minutes and block the editor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "capture": "<capture>"
    },
    "name": "profiler_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoRe-export even if the JSON exists.
folderNoCapture folder. Default: UNITY_PROFILER_CAPTURES or <project>/ProfilerCaptures from the open editor.
captureYesCapture file name (with or without .data) inside the capture folder, or an absolute path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries real weight and does so: it discloses the requirement of an open editor, the concrete output artifact path, and that large captures can take minutes and block the editor. It does not cover failure behavior when the JSON already exists or side effects on the capture itself, but the key operational hazard is surfaced.

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?

Two sentences, front-loaded with the action and the output, followed by the runtime warning. No filler, and the blocking caveat is placed where an agent will see it before deciding to call.

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

Completeness4/5

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

No output schema exists, but the description names the exact produced file, which covers the return-value gap. For a side-effecting tool it also flags the editor dependency and blocking cost; only overwrite/error semantics are left implicit, partly covered by the force parameter in the schema.

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%, so capture, folder, and force are already documented, and the description's only added meaning is that the output name derives from the capture name. Baseline 3 is appropriate.

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?

States a specific verb and resource: load a capture in the open Unity Editor and export per-marker main-thread statistics to a named JSON file. That is concrete enough to distinguish it from summary/compare siblings, though it never names a sibling explicitly to route the agent.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase 'Have the open Unity Editor load a capture' signals the editor must be running, and the file output implies this is for persisting data rather than reading a summary. There is no explicit when-to-use vs when-to-use-profiler_summary or profiler_top_markers guidance.

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