Skip to main content
Glama

get_assets_in_folder

Read-onlyIdempotent

Enumerate every asset in a content folder, recursively by default, returning names, paths, classes, packages, load status, and totals without loading any asset. Use it to inventory a directory.

Instructions

Enumerate every asset under a content FOLDER (recursively by default), each with name, object path, class, package and is_loaded, plus total_found so you can tell a truncated listing from a complete one. The "what is actually in this directory?" inventory -- metadata only, it never loads an asset. Reaches any mounted content root, not just /Game. Pick this over search_assets_by_pattern when you know WHERE to look rather than what the name contains, over get_assets_by_type when you want everything regardless of class, and over resolve_asset_by_name when you do not have an exact name at all.

Returns: { assets: [{ name, path, class, package, is_loaded }], count: int, total_found: int, folder_path: string, recursive: bool, max_results: int, results_truncated: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recursiveNoWhen true (DEFAULT), include subfolders; false lists only the assets sitting directly in this folder
folder_pathYesFolder to list. A bare/relative name is prefixed with /Game/; a path already starting with "/" (e.g. /Water/Materials, /Engine/..., /<PluginName>/...) is used verbatim, so every mounted content root is reachable.
max_resultsNoCap on number of returned assets (1..50000); defaults to 1000. Compare `count` against `total_found` (which is NOT capped) to see how much was left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly spends its words elsewhere: it states 'metadata only, it never loads an asset', that any mounted content root is reachable, and that total_found is uncapped so truncation is detectable. That is genuinely useful context beyond the annotations; it stops short of noting cost/latency on very large folders.

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?

Front-loaded with purpose, then routing, then return shape; every clause carries information. The routing sentence is dense and the return block restates fields already documented in the parameters, which keeps it just shy of maximally tight.

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

Completeness5/5

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

There is no output schema, so the description supplies the full return shape (assets with fields, count, total_found, folder_path, recursive, max_results, results_truncated). Combined with the no-loading guarantee and truncation semantics, an agent has everything needed to call and interpret this correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning: it flags recursion as the default and explains the comparison between count and total_found for detecting an incomplete listing, which the schema only implies. It is reinforcement-plus, not pure repetition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Enumerate every asset under a content FOLDER') with scope modifiers (recursive by default) and enumerates the returned fields. It explicitly distinguishes itself from three named siblings, so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule ('know WHERE to look rather than what the name contains') and names all three alternatives (search_assets_by_pattern, get_assets_by_type, resolve_asset_by_name) with the condition that selects each. This is the when-not/alternative guidance at full strength.

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