Skip to main content
Glama
AnkleBreaker-Studio

Unity MCP Server

by AnkleBreaker-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unity_asset_list

List Unity project assets by folder, type, or search term to find scripts, scenes, prefabs, and materials for AI-driven editing or inspection.

Instructions

List assets in the project. Can filter by path, type, and search term.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoUnity instance port (from unity_select_instance). Always include it when multiple instances run.
typeNoAsset type filter: Script, Scene, Prefab, Material, Texture, AudioClip, AnimationClip, Shader, Font, Mesh, Model
folderNoFolder path relative to Assets/ (default: 'Assets')
searchNoSearch query string
recursiveNoSearch recursively in subfolders (default: true)
maxResultsNoLimit 1-10000 (default 500). Returns totalCount and truncated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.36.0
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum assets to return (default: 500). Use lower values for large projects."New value: +"Limit 1-10000 (default 500). Returns totalCount and truncated."
    • addedInput schema / properties / maxResults / maximum
      Added value: +10000
    • addedInput schema / properties / maxResults / minimum
      Added value: +1
  2. Changed1 schema field changedv2.35.6
    • changedInput schema / properties / port / description
      Previous value: -"Target Unity instance port for parallel-safe routing. Get this from unity_select_instance. When working with multiple Unity instances, ALWAYS include this parameter."New value: +"Unity instance port (from unity_select_instance). Always include it when multiple instances run."
  3. Addedv2.28.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, but the description says nothing about default scope, truncation behavior, or that results are capped (the maxResults schema mentions totalCount/truncated, not the description).

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?

Two short sentences with no filler and the core purpose front-loaded. It is efficient, though the brevity is partly a symptom of thin content rather than disciplined editing.

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

Completeness3/5

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

With six optional parameters, no required parameters, no annotations, and no output schema, a minimal description is survivable because the schema is fully documented. The remaining gap is the unresolved overlap with unity_search_assets, which the description never addresses.

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 every parameter (port, type, folder, search, recursive, maxResults) is already documented in the schema with defaults and bounds. The description names path/type/search but adds no format or default detail beyond what the schema provides; baseline 3 applies.

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 ('List assets in the project') and enumerates the filter axes, so the agent knows exactly what the tool returns. It does not, however, distinguish itself from the sibling unity_search_assets, which appears to do something very similar.

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

Usage Guidelines2/5

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

The sentence 'Can filter by path, type, and search term' hints at capability but gives no when-to-use guidance, no prerequisites, and no routing against the overlapping unity_search_assets sibling. An agent has to guess which of the two list/search tools to call.

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