Skip to main content
Glama

unreal_list_actors

Read-onlyIdempotent

List actors in the currently open Unreal level, returning their labels, paths, and transforms. Use name or class filters and pagination to locate specific actors for further manipulation.

Instructions

List actors placed in the currently open level, with their transforms.

The label field is what other actor tools accept as an identifier, and is what the user sees in the World Outliner.

Args: params (ListActorsInput): Validated input containing: - name_filter (Optional[str]): Substring match on the actor label - class_filter (Optional[str]): Substring match on the actor class - limit (int): Max results, 1-500 (default 50) - offset (int): Results to skip (default 0)

Returns: str: JSON with the following schema: { "total": int, "count": int, "offset": int, "has_more": bool, "next_offset": int | None, "items": [ { "label": str, # Outliner name, use this as an identifier "path": str, # Unique full path "class": str, # e.g. "StaticMeshActor" "location": [float, float, float], # X, Y, Z in cm "rotation": [float, float, float], # pitch, yaw, roll in degrees "scale": [float, float, float] } ] } On failure: "Error: "

Examples: - Use when: "what's in this level?" -> no filters - Use when: finding the exact label to pass to unreal_set_actor_transform - Don't use when: looking for unplaced content (use unreal_list_assets)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, and non-destructive safety information. The description adds important behavioral context beyond that: it operates on the currently open level, the label field is the identifier other actor tools accept, and it specifies both the success JSON schema and the 'Error: <message>' failure format.

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 well-structured and front-loaded with the core purpose. The Args, Returns, and Examples sections each earn their place, and there is no filler or tautology. Despite being detailed, every sentence serves a practical purpose for correct invocation.

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?

The description covers scope, filtering, pagination, output schema, error format, and cross-tool identifier semantics. It also includes usage examples that tie into sibling tools. Nothing needed to call this tool correctly is missing.

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 description documents all nested parameters inside the params object, including substring match semantics, limits, defaults, and offsets. Although the JSON schema already describes these fields, the description packages them in a tool-ready way and adds the crucial note that the label field is used as an identifier by other actor tools.

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?

The description opens with a specific verb and resource: 'List actors placed in the currently open level, with their transforms.' This clearly distinguishes it from sibling tools such as unreal_list_assets, unreal_spawn_actor, and unreal_delete_actor, so an agent can select it confidently.

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?

The Examples section explicitly states when to use the tool ('what's in this level?', finding a label for unreal_set_actor_transform) and when not to use it ('looking for unplaced content (use unreal_list_assets)'). This gives an agent direct routing guidance with a named alternative.

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

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