メニュー
List every scene currently opened in the Unity Editor as a shallow snapshot (name, path, build flags). Use 'scene-get-data' for the deep view of a specific scene.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | scene-list-opened |
| description | List every scene currently opened in the Unity Editor as a shallow snapshot (name, path, build flags). Use 'scene-get-data' for the deep view of a specific scene. |
Returns the list of currently opened scenes in Unity Editor. Use 'scene-get-data' tool to get detailed information about a specific scene.
Maps OpenedScenes through ToSceneDataShallow() on the main thread and returns the resulting array. No filtering or pagination — every opened scene is included.
unity-mcp-cli run-tool scene-list-opened --input '{
"nothing": "string_value"
}'
For complex input (multi-line strings, code), save the JSON to a file and use:
unity-mcp-cli run-tool scene-list-opened --input-file args.jsonOr pipe via stdin (recommended):
unity-mcp-cli run-tool scene-list-opened --input-file - <<'EOF' {"param": "value"} EOF
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.
| Name | Type | Required | Description |
|---|---|---|---|
nothing | string | No |
{
"type": "object",
"properties": {
"nothing": {
"type": "string"
}
}
}
{
"type": "object",
"properties": {
"result": {
"$ref": "#/$defs/AIGD.SceneDataShallow-1"
}
},
"$defs": {
"AIGD.SceneDataShallow": {
"type": "object",
"properties": {
"Name": {
"type": "string"
},
"IsLoaded": {
"type": "boolean"
},
"IsDirty": {
"type": "boolean"
},
"IsSubScene": {
"type": "boolean"
},
"IsValidScene": {
"type": "boolean",
"description": "Whether this is a valid Scene. A Scene may be invalid if, for example, you tried to open a Scene that does not exist. In this case, the Scene returned from EditorSceneManager.OpenScene would return False for IsValid."
},
"RootCount": {
"type": "integer"
},
"path": {
"type": "string",
"description": "Path to the Scene within the project. Starts with 'Assets/'"
},
"buildIndex": {
"type": "integer",
"description": "Build index of the Scene in the Build Settings."
},
"instanceID": {
"type": "integer",
"description": "instanceID of the UnityEngine.Object. If this is '0', then it will be used as 'null'."
}
},
"required": [
"IsLoaded",
"IsDirty",
"IsSubScene",
"IsValidScene",
"RootCount",
"buildIndex",
"instanceID"
],
"description": "Scene reference. Used to find a Scene."
},
"AIGD.SceneDataShallow-1": {
"type": "array",
"items": {
"$ref": "#/$defs/AIGD.SceneDataShallow",
"description": "Scene reference. Used to find a Scene."
}
}
},
"required": [
"result"
]
}
Modify an asset file in the project. Use 'assets-get-data' first to inspect the asset structure before modifying. Not allowed to modify asset files in the 'Packages/' folder — modify them in 'Assets/'. Three modification surfaces are available (content, pathPatches, jsonPatch) — see the skill body for details.
Modify a specific Component on a GameObject in opened Prefab or in a Scene. Allows direct modification of component fields and properties without wrapping in GameObject structure. Use 'gameobject-component-get' first to inspect the component structure before modifying. Three modification surfaces are available (componentDiff, pathPatches, jsonPatch) — see the skill body for details.
Modify a Unity `UnityEngine.Object`'s serializable fields/properties. Three modification surfaces are available (`objectDiff`, `pathPatches`, `jsonPatch`) — see the skill body. Use 'object-get-data' first to inspect the object structure.
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.
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).
Delete the assets at the given project paths. Refreshes the AssetDatabase at the end. Use 'assets-find' to locate the assets first.