Skip to main content
Glama
NAJEMWEHBE

unreal-ai-connection

bulk_fix_redirectors

Resolve UObjectRedirector stubs across multiple content folders in a single call. Useful after bulk asset moves or renames to clean up redirectors without per-folder commands.

Instructions

Resolve UObjectRedirector stubs across multiple content folders in one MCP call. Composes fix_up_redirectors per folder. Useful as a follow-up to a sweep of bulk_move_assets / bulk_rename_assets calls (each of which leaves redirectors at the source paths) so the LLM does not have to issue one fix_up_redirectors per touched folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
foldersYesContent folder paths under which to fix up redirectors (e.g. ['/Game/Materials', '/Game/Textures']). Each non-empty, NUL + '..' segments rejected, max 100 entries.
recursiveNoDefault true. Echoed back in the response for clarity; fix_up_redirectors itself always operates recursively under the supplied path -- this field exists so callers can capture intent without having to track it separately.
continue_on_errorNoDefault true. When false, stop at the first per-folder fix-up failure and emit halted_at_index.
Behavior4/5

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

Describes composition of fix_up_redirectors per folder and explains parameter behaviors (recursive echoed, continue_on_error control), adding value beyond schema.

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?

Two sentences: one for purpose, one for usage guidance. No wasted words.

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

Completeness4/5

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

Given no output schema, description sufficiently covers behavior and use cases; missing return value info but acceptable for this tool.

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?

Adds meaning beyond schema by explaining recursive's purpose for intent capture and continue_on_error's stopping behavior; schema coverage is 100%.

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?

Clearly states tool resolves UObjectRedirector stubs across multiple folders, distinguishing from sibling fix_up_redirectors which operates on a single folder.

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?

Explicitly advises to use as follow-up to bulk_move_assets/bulk_rename_assets, implying alternative fix_up_redirectors for single folders.

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/NAJEMWEHBE/unreal-ai-connection'

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