/unity-tool-list
List all Unity-MCP tools registered in the connected Unity Editor instance. Optional regex filter matches against tool name, description, and argument names/descriptions. Use the `includeDescription` / `includeInputs` toggles to control the response size.
$ npx -y skills add IvanMurzak/Unity-MCP --skill unity-tool-list --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/unity-tool-list
Context preview
The summary Claude sees to decide when to auto-load this skill.
List all Unity-MCP tools registered in the connected Unity Editor instance. Optional regex filter matches against tool name, description, and argument names/descriptions. Use the `includeDescription` / `includeInputs` toggles to control the response size.
SKILL.md
unity-tool-list.SKILL.mdname: unity-tool-list
description: List all Unity-MCP tools registered in the connected Unity Editor instance. Optional regex filter matches against tool name, description, and argument names/descriptions. Use the `includeDescription` / `includeInputs` toggles to control the response size.
Tool / List
List all Unity-MCP tools registered in the connected Unity Editor instance. Optionally filter by regex across tool names, descriptions, and arguments.
Inputs
- `regexSearch` (optional) — case-insensitive regex with a 200ms execution-timeout guard. Invalid regex throws an `ArgumentException`. Matches name → description → input names → input descriptions.
- `includeDescription` (default `false`) — populate each tool's `Description` field.
- `includeInputs` (default `None`) — one of `None`, `Inputs` (names only), `InputsWithDescription` (names + descriptions).
Behavior
Iterates `UnityMcpPluginEditor.Instance.Tools.GetAllTools()`, evaluates the filter (if any), and projects each surviving tool into a `ToolInfoData` honoring the verbosity toggles.
How to Call
unity-mcp-cli run-tool unity-tool-list --input '{
"regexSearch": "string_value",
"includeDescription": "string_value",
"includeInputs": "string_value"
}'> For complex input (multi-line strings, code), save the JSON to a file and use: > ```bash > unity-mcp-cli run-tool unity-tool-list --input-file args.json > ``` > > Or pipe via stdin (recommended): > ```bash > unity-mcp-cli run-tool unity-tool-list --input-file - <<'EOF' > {"param": "value"} > EOF > ```
Troubleshooting
If `unity-mcp-cli` is not found, either install it globally (`npm install -g unity-mcp-cli`) or use `npx unity-mcp-cli` instead. Read the /unity-initial-setup skill for detailed installation instructions.
Input
| Name | Type | Required | Description | |------|------|----------|-------------| | `regexSearch` | `string` | No | Regex pattern to filter tools. Matches against tool name, description, and argument names and descriptions. | | `includeDescription` | `any` | No | Include tool descriptions in the result. Default: false | | `includeInputs` | `any` | No | Include input arguments in the result. Default: None |
Input JSON Schema
{
"type": "object",
"properties": {
"regexSearch": {
"type": "string"
},
"includeDescription": {
"$ref": "#/$defs/System.Boolean"
},
"includeInputs": {
"$ref": "#/$defs/com.IvanMurzak.Unity.MCP.Editor.API.Tool_Tool-InputRequest"
}
},
"$defs": {
"System.Boolean": {
"type": "boolean"
},
"com.IvanMurzak.Unity.MCP.Editor.API.Tool_Tool-InputRequest": {
"type": "string",
"enum": [
"None",
"Inputs",
"InputsWithDescription"
],
"description": "Specifies what to include for tool input arguments."
}
}
}Output
Output JSON Schema
{
"type": "object",
"properties": {
"result": {
"$ref": "#/$defs/AIGD.ToolInfoData-1"
}
},
"$defs": {
"AIGD.ToolInfoData": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Tool name."
},
"description": {
"type": "string",
"description": "Tool description."
},
"inputs": {
"$ref": "#/$defs/AIGD.ToolInputData-1",
"description": "Tool input arguments."
}
},
"description": "MCP tool information."
},
"AIGD.ToolInputData-1": {
"type": "array",
"items": {
"$ref": "#/$defs/AIGD.ToolInputData",
"description": "MCP tool input argument."
}
},
"AIGD.ToolInputData": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Argument name."
},
"description": {
"type": "string",
"description": "Argument description."
}
},
"description": "MCP tool input argument."
},
"AIGD.ToolInfoData-1": {
"type": "array",
"items": {
"$ref": "#/$defs/AIGD.ToolInfoData",
"description": "MCP tool information."
}
}
},
"required": [
"result"
]
}Read more
name: unity-tool-list description: List all Unity-MCP tools registered in the connected Unity Editor instance. Optional regex filter matches against tool name, description, and argument names/descriptions. Use the `includeDescription` / `includeInputs` toggles to control the response size.
Tool / List
List all Unity-MCP tools registered in the connected Unity Editor instance. Optionally filter by regex across tool names, descriptions, and arguments.
Inputs
- `regexSearch` (optional) — case-insensitive regex with a 200ms execution-timeout guard. Invalid regex throws an `ArgumentException`. Matches name → description → input names → input descriptions.
- `includeDescription` (default `false`) — populate each tool's `Description` field.
- `includeInputs` (default `None`) — one of `None`, `Inputs` (names only), `InputsWithDescription` (names + descriptions).
Behavior
Iterates `UnityMcpPluginEditor.Instance.Tools.GetAllTools()`, evaluates the filter (if any), and projects each surviving tool into a `ToolInfoData` honoring the verbosity toggles.
How to Call
unity-mcp-cli run-tool unity-tool-list --input '{
"regexSearch": "string_value",
"includeDescription": "string_value",
"includeInputs": "string_value"
}'> For complex input (multi-line strings, code), save the JSON to a file and use: > ```bash > unity-mcp-cli run-tool unity-tool-list --input-file args.json > ``` > > Or pipe via stdin (recommended): > ```bash > unity-mcp-cli run-tool unity-tool-list --input-file - <<'EOF' > {"param": "value"} > EOF > ```
Troubleshooting
If `unity-mcp-cli` is not found, either install it globally (`npm install -g unity-mcp-cli`) or use `npx unity-mcp-cli` instead. Read the /unity-initial-setup skill for detailed installation instructions.
Input
| Name | Type | Required | Description | |------|------|----------|-------------| | `regexSearch` | `string` | No | Regex pattern to filter tools. Matches against tool name, description, and argument names and descriptions. | | `includeDescription` | `any` | No | Include tool descriptions in the result. Default: false | | `includeInputs` | `any` | No | Include input arguments in the result. Default: None |
Input JSON Schema
{
"type": "object",
"properties": {
"regexSearch": {
"type": "string"
},
"includeDescription": {
"$ref": "#/$defs/System.Boolean"
},
"includeInputs": {
"$ref": "#/$defs/com.IvanMurzak.Unity.MCP.Editor.API.Tool_Tool-InputRequest"
}
},
"$defs": {
"System.Boolean": {
"type": "boolean"
},
"com.IvanMurzak.Unity.MCP.Editor.API.Tool_Tool-InputRequest": {
"type": "string",
"enum": [
"None",
"Inputs",
"InputsWithDescription"
],
"description": "Specifies what to include for tool input arguments."
}
}
}Output
Output JSON Schema
{
"type": "object",
"properties": {
"result": {
"$ref": "#/$defs/AIGD.ToolInfoData-1"
}
},
"$defs": {
"AIGD.ToolInfoData": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Tool name."
},
"description": {
"type": "string",
"description": "Tool description."
},
"inputs": {
"$ref": "#/$defs/AIGD.ToolInputData-1",
"description": "Tool input arguments."
}
},
"description": "MCP tool information."
},
"AIGD.ToolInputData-1": {
"type": "array",
"items": {
"$ref": "#/$defs/AIGD.ToolInputData",
"description": "MCP tool input argument."
}
},
"AIGD.ToolInputData": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Argument name."
},
"description": {
"type": "string",
"description": "Argument description."
}
},
"description": "MCP tool input argument."
},
"AIGD.ToolInfoData-1": {
"type": "array",
"items": {
"$ref": "#/$defs/AIGD.ToolInfoData",
"description": "MCP tool information."
}
}
},
"required": [
"result"
]
}Get up and running in three steps: Install plugin — download the .unitypackage installer or run openupm add com.ivanmurzak.unity.mcp Alternative: npx unity-mcp-cli install-plugin ./MyUnityProject — see CLI documentation Pick an AI agent — Claude Code, Claude
Repo: IvanMurzak/Unity-MCP
Other skills on ivanmurzak-unity-mcp.
- /build-cli
Build the unity-mcp-cli TypeScript CLI tool and link it globally for terminal use.
Open skill - /github-pr-review-fix
Review and resolve PR comments from GitHub. Validates each comment, fixes legitimate issues.
Open skill - /assets-copy
Copy assets at given paths and store them at new paths. Refreshes the AssetDatabase at the end. Use 'assets-find' to locate the source assets first.
Open skill - /assets-create-folder
Create a new folder under a parent folder inside 'Assets/'. The parent path must start with 'Assets/' and every intermediate folder in it must already exist. Refreshes the AssetDatabase at the end and returns the GUID(s) of the created folder(s).
Open skill - /assets-delete
Delete the assets at the given project paths. Refreshes the AssetDatabase at the end. Use 'assets-find' to locate the assets first.
Open skill - /assets-find-built-in
Search the built-in assets of the Unity Editor (located at Resources/unity_builtin_extra). Filters by name and/or type; built-in assets have no GUID so GUID-based lookups are not supported.
Open skill

