Skip to main content
Glama

unreal_reimport_asset

Reimports an existing asset to refresh its content from the original source file, updating the Unreal Engine 5 project after source changes.

Instructions

Reimport an asset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "unreal_reimport_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing. It does not say whether reimport overwrites existing asset modifications, requires a loaded editor/content browser, needs the source file to be present, or is destructive or reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is short, but that brevity reflects under-specification rather than economy. There is no front-loaded scope or routing information, so nothing meaningful was trimmed to achieve it.

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

Completeness1/5

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

For a mutation tool with an opaque object parameter, no annotations, and no guidance, the definition is far too thin; the existence of an output schema only excuses return-value explanation. An agent would have to guess the parameter's shape and the operation's side effects before calling it.

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

Parameters1/5

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

The single required parameter "params" has 0% schema description coverage and its type is unconstrained, while the description adds nothing about what it should contain (asset path, source file, import options). The one place the description could have compensated for a bare schema is left empty.

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

Purpose2/5

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

"Reimport an asset" restates the tool name almost verbatim and adds no scope, target, or outcome detail. It does not distinguish this from siblings such as unreal_import_asset or unreal_reimport_blender_asset, so an agent cannot tell which import path applies.

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

Usage Guidelines1/5

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

There is no when-to-use, when-not-to-use, or prerequisite guidance. The definition gives no basis for choosing reimport over a fresh import or the blender-specific reimport variant, even though those siblings are visible.

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