Skip to main content
Glama
Flux-Point-Studios

Unreal Engine MCP Server

manage_tasks

Manage queued tasks for long-running Unreal Engine operations. Submit, monitor, retrieve results, cancel, and clean up.

Instructions

Async task queue for long-running operations. Submit tool calls for background execution, poll status, retrieve results. Use for operations that may take 30+ seconds (landscape sculpting, asset imports, blueprint compilation). Actions: submit (queue a tool call), status (check progress), result (get output), list (show all tasks), cancel (abort task), cleanup (remove old tasks).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments object to pass to the target tool (for submit action)
actionYessubmit: queue a tool for async execution. status: check task progress. result: get completed task output. list: show all tasks. cancel: abort a pending/running task. cleanup: remove old completed tasks.
task_idNoTask ID to query (for status, result, cancel actions)
tool_nameNoTarget tool name to execute (for submit action, e.g. build_environment, manage_asset)
status_filterNoFilter tasks by status (for list action)
target_actionNoAction to pass to the target tool (for submit action, e.g. sculpt_landscape, import)
max_age_secondsNoMax age in seconds for cleanup (default 300). Tasks older than this are removed (for cleanup action).
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses core asynchronous behaviors: background execution, polling, result retrieval, cancellation, and cleanup. However, it omits details about the submit response (e.g., it returns a task_id) and error handling, which are relevant for a queue tool.

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 compact—two sentences plus a concise action list—and front-loads the core purpose. Every sentence contributes meaning, and the structure is easy to scan.

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

Completeness3/5

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

The description explains the overall workflow but misses the critical link that submitting a task returns a task_id for use with status/result/cancel. The schema mentions task_id for queries but not its origin in the submit response. Given the tool's multi-action complexity, this gap leaves a user uncertain about how to chain actions.

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

Parameters3/5

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

The input schema has 100% coverage with descriptions for all 7 parameters, so the baseline is 3. The description repeats the action names but adds only marginal context (e.g., 'submit: queue a tool call') without providing new parameter-level semantics beyond the schema's own examples.

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's purpose as an async task queue for long-running operations, with a specific list of actions (submit, status, result, list, cancel, cleanup). It distinguishes itself from sibling manage_* tools by focusing on task management rather than specific asset types.

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

Usage Guidelines4/5

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

The description provides explicit usage context: 'Use for operations that may take 30+ seconds (landscape sculpting, asset imports, blueprint compilation).' It does not explicitly name alternative tools or when not to use, but the timing guidance gives clear context for choosing this tool over synchronous execution.

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