Skip to main content
Glama

editor_list_assets

Retrieve a list of all Unreal Engine asset paths to manage and organize project content efficiently.

Instructions

List all Unreal assets

Example output: [''/Game/Characters/Hero/BP_Hero'', ''/Game/Maps/TestMap'', ''/Game/Materials/M_Basic'']

Returns a Python list of asset paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the editor_list_assets tool with the MCP server, including description and the handler function that executes the tool by running the generated Python command.
    server.tool(
    	"editor_list_assets",
    	"List all Unreal assets\n\nExample output: [''/Game/Characters/Hero/BP_Hero'', ''/Game/Maps/TestMap'', ''/Game/Materials/M_Basic'']\n\nReturns a Python list of asset paths.",
    	async () => {
    		const result = await tryRunCommand(editorTools.UEListAssets())
    		return {
    			content: [
    				{
    					type: "text",
    					text: result,
    				},
    			],
    		}
    	},
    )
  • Helper function UEListAssets that reads and templates the Python script for listing assets.
    export const UEListAssets = () => Template(read("./scripts/ue_list_assets.py"))
  • The core implementation logic in Python: lists all assets recursively in /Game folder using Unreal's EditorAssetLibrary and prints the list, which is executed remotely in the Unreal Editor.
    from typing import List
    import unreal
    
    
    def list_assets() -> List[str]:
        assets = unreal.EditorAssetLibrary.list_assets("/Game", recursive=True)
        return assets
    
    
    def main():
        assets = list_assets()
        print(assets)
    
    
    if __name__ == "__main__":
        main()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool lists assets and returns a Python list, but lacks critical behavioral details: it doesn't specify if this is a read-only operation, potential performance impacts for large projects, or any limitations. For a tool with zero annotation coverage, this is inadequate.

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?

The description is highly concise and well-structured: it starts with the core purpose, provides a concrete example output, and clarifies the return type. Every sentence adds value without redundancy, making it easy to parse quickly.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does and the return format, but lacks context on usage guidelines and behavioral transparency, which are important for completeness even in simple cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here. Baseline is 4 for zero parameters, as no compensation is needed.

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?

The description clearly states the verb 'List' and resource 'all Unreal assets', making the purpose specific and understandable. It distinguishes from siblings like 'editor_search_assets' by implying a comprehensive listing without filtering, though not explicitly named. However, it lacks explicit sibling differentiation, preventing a perfect score.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention when to choose this over 'editor_search_assets' for filtered results or other asset-related tools, leaving usage context unclear. This is a significant gap in practical utility.

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/runreal/unreal-mcp'

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