Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_timeline_to_blueprint

Creates both the Timeline variable and node for an Actor Blueprint, sets its length, compiles, and verifies the timeline was registered.

Instructions

Add a Timeline to an Actor Blueprint: creates BOTH the UTimelineTemplate variable and its UK2Node_Timeline node in one call, sets a fixed length in seconds, compiles, and verifies the template really registered (timeline_created). Actor-derived Blueprints only. It does NOT author curves or tracks -- the node comes with Play/Stop/Reverse inputs and Update/Finished outputs and nothing driven; a requested name already in use is silently uniquified, so wire the RETURNED timeline_name.

Returns: { node_id, class, title, pins:[...], blueprint_name, graph_name, timeline_name, length, timeline_created, timeline_guid } -- timeline_name is the name ACTUALLY used and timeline_created is a post-compile re-lookup of the template, so false means the variable did not survive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoOptional. This command is REFUSED while a Play-in-Editor session is running: it either compiles a Blueprint (the reinstancer can retain a world, and CheckForWorldGCLeaks is Fatal -- it KILLS the editor) or writes to disk (Editor.AllowSavingAssetsDuringPIE=0 makes the engine refuse the write, so it would report success without writing a byte). Stop PIE and retry instead; force=true runs it anyway, at your own risk.
lengthNoTimeline length in seconds (sets fixed-length mode); defaults to 5.0
graph_nameNoTarget graph name; defaults to the Blueprint's event graph when omitted
position_xNoNode X position on the graph canvas (ignored when node_position is set)
position_yNoNode Y position on the graph canvas (ignored when node_position is set)
node_positionNoNode canvas position as [x, y]; takes precedence over position_x/position_y
timeline_nameYesDesired variable name for the timeline; if it is taken, a unique one is generated and returned instead.
blueprint_nameNoName (or full object path) of an Actor Blueprint.
blueprint_pathNoAlias of `blueprint_name` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `blueprint_name`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark it as a non-readonly, non-idempotent, non-destructive write; the description adds substantial context: it compiles the Blueprint, silently uniquifies an in-use name (with the warning to wire the returned timeline_name), and explains that timeline_created is a post-compile re-lookup whose false value means the variable did not survive. This is behavior an agent could not infer from the annotations.

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

Conciseness4/5

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

Front-loaded with the core action in the first clause, and the trailing Returns block earns its space by defining timeline_name and timeline_created semantics. The prose is dense but not padded; only the pin/track enumeration is slightly verbose.

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

Completeness5/5

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

With no output schema, the description supplies a full Returns contract, discloses the critical silent-uniquify edge case, and (via the force param) explains the PIE refusal. Everything an agent needs to invoke this mutation correctly and interpret its result is present.

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 coverage is 100%, so the schema already carries most parameter meaning. The description still adds actionable semantics: that length puts the timeline in fixed-length mode and that the returned timeline_name is the one actually used (not the requested one), which is the key invocation detail.

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?

States a specific verb and resource and enumerates exactly what a single call produces: the UTimelineTemplate variable, the UK2Node_Timeline node, a fixed length, a compile, and a registration check. It is clearly distinguishable from graph-building siblings like build_blueprint_graph or add_anim_graph_node without opening either schema.

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?

Gives scoping conditions ('Actor-derived Blueprints only') and an explicit negative scope ('It does NOT author curves or tracks'), which tells the agent when this tool is not the right fit. It does not name a sibling alternative for the curve-authoring case, so it stops short of full when/when-not routing.

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