Skip to main content
Glama
aadeshrao123

Unreal-MCP

by aadeshrao123

set_actor_property

Set any nested property on a placed actor instance in the level, preserving editor overrides and marking the level dirty.

Instructions

Set a property at any nested path on a placed level actor instance.

Writes to the actual placed actor (not its CDO/Blueprint defaults), so editor overrides are preserved. Walks struct fields and array indices, fires PostEditChangeProperty on the top-level property, and marks the level dirty.

Args: actor_label: Actor's display label in the Outliner (or its UObject name). property_path: Dot-separated property path. Examples: "Settings.BloomIntensity" "Settings.ColorGradingHighlights.Gain" "Tags[0]" "Settings.bOverride_BloomIntensity" property_value: The value to write. Accepts: - Numbers, bools, strings for primitives and enums - JSON object for structs ({"R":1.0,"G":0.5,"B":0.0,"A":1.0} for FLinearColor) - UE text format string for structs ("(R=1.0,G=0.5,B=0.0,A=1.0)") - Asset path string for object/class references component_name: Optional. If set, the path is resolved starting from a component on the actor instead of the actor itself.

Returns: actor identification + the resolved top-level FProperty name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actor_labelYes
property_pathYes
component_nameNo
property_valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description fully discloses behavioral traits: writes to actual placed actor, preserves editor overrides, walks struct fields and array indices, triggers PostEditChangeProperty, and marks level dirty. This is comprehensive given no annotations.

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 with clear sections, bullet points, and examples. Every sentence adds value, and the key information is front-loaded.

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?

Given the complexity of nested property paths and multiple value formats, the description covers all necessary details: parameters, return value, and behavioral effects. It is complete for an agent to use correctly.

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

Parameters5/5

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

With 0% schema coverage, the description adds critical meaning: explains actor_label, provides property_path examples, enumerates accepted value formats for property_value, and clarifies component_name. This significantly compensates for schema gaps.

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 clearly states the tool sets a property at any nested path on a placed level actor instance, using specific verbs and resources. It distinguishes from siblings by focusing on actor properties, as opposed to assets or blueprints.

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

Usage Guidelines3/5

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

The description explains how to use the tool with detailed parameter descriptions and examples, but does not provide explicit guidance on when to use this tool versus alternatives like set_asset_property. Usage context is implied but not explicitly stated.

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/aadeshrao123/Unreal-MCP'

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