Skip to main content
Glama

unreal_render_sequence

Queue a sequence render or export in Unreal Engine 5, letting you trigger cinematic or Level Sequence output from an AI client without leaving the editor workflow.

Instructions

Queue a sequence render/export.

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_render_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Queue' hints that the render is enqueued rather than executed synchronously, but nothing is said about how to poll for completion, whether the call blocks, what happens to an existing queue, or what permissions/output paths are involved.

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

Conciseness3/5

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

A single short sentence with no filler and the action front-loaded, but its brevity reflects under-specification rather than efficiency given how little the agent learns.

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?

An output schema exists, so return values need not be explained, but the tool takes an opaque params object that the agent cannot populate from this definition. For a render/export operation with no annotations, the definition leaves out essentials like output destination and sequencing context.

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?

The single required parameter is an untyped object named 'params' with 0% schema description coverage, and the description adds no indication of what fields it expects (sequence path, output directory, format, frame range). With low coverage the description is required to compensate, and here it does not.

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?

States a specific verb ('queue') and resource ('sequence render/export'), so the agent knows this initiates rendering of a sequence rather than a single frame. It does not explicitly distinguish itself from the sibling unreal_render_image or unreal_capture_screenshot, which would remove ambiguity about which render entry point to pick.

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?

There is no guidance on when to choose this over unreal_render_image or unreal_get_render_settings, nor any prerequisite such as configuring render settings first. The word 'Queue' weakly implies asynchronous execution but no when-to-use condition is stated.

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