Skip to main content
Glama
Flux-Point-Studios

Unreal Engine MCP Server

manage_asset

Destructive

Create, import, duplicate, rename, delete assets; edit material graphs and instances; analyze dependencies for Unreal Engine projects.

Instructions

Create, import, duplicate, rename, delete assets. Edit Material graphs and instances. Analyze dependencies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
tagNoName of the tag.
descNo
nameNoName identifier.
pathNoPath to a directory.
posXNo
posYNo
saveNoSave the asset(s) after the operation.
tagsNo
typeNo
limitNo
nodesNo
pathsNo
toPinNoName of the target pin.
valueNoGeneric value (any type).
widthNo
actionYesAction to perform. Use dump_asset to serialize a UObject/DataAsset properties to JSON for inspection.
formatNo
heightNo
nodeIdNoID of the node.
prefixNo
suffixNo
commentNo
fromPinNoName of the source pin.
newNameNoNew name for renaming.
pinNameNoName of the pin.
inputPinNoName of the target pin.
lodCountNo
maxDepthNo
meshPathNoMesh asset path.
metadataNo
nodeNameNoName identifier.
nodeTypeNo
toNodeIdNoID of the target node.
assetPathNoAsset path (e.g., /Game/Path/Asset).
directoryNoPath to a directory.
eventNameNoName of the event.
graphNameNoName of the graph.
inputNameNoName of the pin.
outputPinNoName of the source pin.
overwriteNoOverwrite if the asset/file already exists.
assetPathsNo
classNamesNo
folderPathNoPath to a directory.
fromNodeIdNoID of the source node.
parametersNo
searchTextNo
sourceNodeNoID of the source node.
sourcePathNoSource path for import/move/copy.
targetNodeNoID of the target node.
childNodeIdNoID of the node.
descriptionNo
memberClassNo
replaceTextNo
texturePathNoTexture asset path.
defaultValueNoGeneric value (any type).
includeNullsNoInclude null/empty values (default: false)
materialPathNoMaterial asset path.
packagePathsNo
parentNodeIdNoID of the node.
sourceNodeIdNoID of the source node.
targetNodeIdNoID of the target node.
checkoutFilesNo
directoryPathNoPath to a directory.
maxMapEntriesNoMax map entries to serialize (default: 200)
parameterNameNoName of the parameter.
parameterTypeNo
parentMaterialNoMaterial asset path.
recursivePathsNo
coordinateIndexNo
destinationPathNoDestination path for move/copy.
expressionClassNo
expressionIndexNoID of the node.
fixupRedirectorsNo
includeTransientNoInclude transient properties (default: false)
maxArrayElementsNoMax array elements to serialize (default: 200)
recursiveClassesNo
showConfirmationNo
propertyAllowlistNoOnly include these property names
reductionSettingsNo
Behavior3/5

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

Annotations already declare destructiveHint=true, and the description adds operation context such as deleting assets and editing materials. It does not, however, detail what gets destroyed, side effects, or consequences of source-control-related actions, so the added behavioral transparency is limited.

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 three tightly written sentences with no filler, front-loading the main operations. It is concise and well-structured for a broad tool, though it sacrifices detail.

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

Completeness2/5

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

With 81 parameters, over 50 actions, and no output schema, this high-level description is insufficient for an agent to select and invoke the right action. It omits return values, parameter relationships, and action-specific behavior.

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

Parameters2/5

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

Schema description coverage is only 54% across 81 parameters, and the description itself provides no parameter-level meaning. It does not compensate for the many undocumented or sparsely documented parameters like checkoutFiles, fixupRedirectors, or reductionSettings.

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 uses specific verbs and resources: 'Create, import, duplicate, rename, delete assets. Edit Material graphs and instances. Analyze dependencies.' It clearly states the tool's functional scope and is distinguishable from pure material or texture tools, though it doesn't explicitly name alternatives.

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?

No explicit guidance on when to use this tool versus sibling tools like manage_material_authoring or manage_texture. The description implies asset management usage but does not provide selection criteria for the many actions or exclusions.

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/Flux-Point-Studios/unreal-mcp'

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