Skip to main content
Glama

Export assets from a package

umodel_export

Export Unreal Engine game assets to standard formats (PSK/GLTF/TGA/PNG) via umodel. Handles entire packages or selected objects, and requires a game tag for cooked UE4/5 titles.

Instructions

Run 'umodel -export' to convert assets (meshes, textures, animations, sounds...) to standard formats (psk/gltf/tga/png/...). Without object filters the whole package is exported. Output defaults to the Downloads folder. IMPORTANT: cooked UE4/5 games need a gameTag, otherwise umodel pops a blocking engine-version GUI dialog. ALWAYS call umodel_game_list { tags: true } FIRST and use the official tag if the game is listed (e.g. roco); the server blocks the call and reminds you if gameTag is missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outNoOutput directory (-out=). Defaults to session outputDir or Downloads/umodel-export.
jsonNoReturn machine-readable JSON instead of formatted text.
lodsNoExport all mesh LOD levels (-lods)
groupsNoUse group names for directories instead of class names (-groups, UE1-3)
objectNoSingle object name to export (positional <object>)
soundsNoAllow sound export (-sounds)
uncookNoUse original package names for output dirs (-uncook, UE3)
aesKeysNoAES keys for encrypted pak files (-aes=). Overrides session.
gameTagNoGame tag override (-game=), e.g. ue4.27 or an official tag like roco. Cooked UE4/5 games REQUIRE a tag — without it umodel pops a blocking GUI dialog. See umodel_game_list.
objectsNoAdditional object filters (-obj=name, repeatable)
packageYesPackage name, wildcard, or full file path
scriptsNoExport UnrealScript as .uc (-uc)
gamePathNoGame installation directory (-path=). Overrides session. If unknown, ask the user first.
classNameNoClass of the object (positional <class>)
timeoutMsNoOverride invocation timeout (ms)
meshFormatNoMesh export format (default psk)
thirdPartyNoAllow 3rd-party asset export: ScaleForm/FaceFX (-3rdparty)
noOverwriteNoDo not overwrite existing files (-nooverwrite)
textureFormatNoTexture format (default tga; dds keeps original compression)
Behavior4/5

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

With no annotations, the description discloses important behaviors: whole package export by default, output defaults to Downloads, blocking GUI dialog if gameTag missing, and server-side validation. This goes beyond the schema and alerts the agent to mandatory prerequisites, though it doesn't detail error responses or output structure.

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?

Three sentences cover the essential command, default behavior, and a critical warning. No filler; each sentence earns its place and the most important instruction is front-loaded.

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?

For a 19-parameter tool with no annotations or output schema, the description covers the most critical operational details (default output, gameTag requirement, whole-package behavior). It omits return value structure but remains sufficient for selection and invocation.

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?

Schema has 100% parameter descriptions, but the description adds contextual meaning: object filters control whether the whole package is exported, and gameTag is critical for cooked games. This clarifies the semantics of key parameters beyond their schema descriptions.

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 converts assets from a package to standard formats, with a specific command example ('umodel -export'). It distinguishes from sibling listing tools by focusing on export/convert behavior, not listing.

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?

It explicitly instructs to call umodel_game_list { tags: true } first for cooked UE4/5 games and warns that the server blocks the call if gameTag is missing. This provides clear when-to-use guidance and a prerequisite that affects tool selection.

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/CHA1007/Umodel-MCP'

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