Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

remove_keyframe

Destructive

Delete a keyframe by index or frame from a Level Sequence binding's section channel, with out-of-range guards returning clean errors instead of crashes.

Instructions

Remove one keyframe (located by 'index' or 'frame') from a binding's section channel (resolved like move_keyframe). The out-of-range guard is applied BEFORE RemoveKey because TMovieSceneChannelData::RemoveKey has a fatal check(IsValidIndex) -- an invalid locator returns a clean error, never a crash. channel_type selects the proxy view ("double" default | "float" | "bool").

Returns: { sequence_path: string, channel_type: string, channel_index: int, removed_frame: int, key_index: int, removed: bool, key_count_after: int, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameNoFrame of the key to remove (resolved via FindKey; provide index OR frame).
indexNoIndex of the key to remove (mutually exclusive with frame).
toleranceNoOptional FindKey frame tolerance when locating by frame (default 0).
track_typeNoOptional class filter (see set_section_easing) selecting the track on the binding.
track_indexNoIndex into the binding's tracks (default 0; used when track_type omitted).
binding_guidNoGUID of the binding whose section to edit.
channel_typeNoChannel value kind: "double" (default) | "float" | "bool".
channel_indexNoIndex of the channel within its proxy view (default 0).
section_indexNoIndex of the section on the resolved track (default 0).
sequence_nameNoAlias for sequence_path.
sequence_pathNoFull /Game path OR bare asset name of the target Level Sequence.
binding_name_or_guidNoAlias for binding_guid, read only when binding_guid is absent; it must also be a GUID string, a bound object's name is not resolved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / binding_name_or_guid / description
      Previous value: -"Sequencer binding: the bound object's name or its GUID string."New value: +"Alias for binding_guid, read only when binding_guid is absent; it must also be a GUID string, a bound object's name is not resolved."
    • removedInput schema / required
      Removed value: -[
-  "sequence_path",
-  "binding_guid"
-]
  2. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructive=true and non-idempotent, so the safety bar is lowered. The description still adds real value beyond them: the out-of-range guard runs before RemoveKey, an invalid locator yields a clean error rather than a crash, and the Returns block reveals that the operation persists a save (saved / save_error).

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?

The core action is front-loaded, followed by resolution and safety notes and a Returns block. It is dense but mostly earns its space; the internal C++ references (TMovieSceneChannelData::RemoveKey, check(IsValidIndex)) are slightly verbose for an agent audience.

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, the description compensates by spelling out the return object, and annotations cover the safety profile. With 12 fully documented parameters and a stated error/save model, an agent has enough to call it correctly; only explicit when-to-use guidance is missing.

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?

Schema description coverage is 100%, so the schema already documents all 12 parameters, including channel_type default and the frame/index mutual exclusion. The description restates channel_type and the index/frame locator but adds no format or validation detail beyond the schema, so the baseline 3 is appropriate.

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 (Remove) and resource (one keyframe) plus its locator mechanism (index or frame) and target (a binding's section channel). It also anchors semantics to a sibling ('resolved like move_keyframe'), letting an agent distinguish it from move_keyframe and duplicate_keyframe without opening schemas.

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

Usage Guidelines3/5

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

The description explains how to locate the key (index OR frame) and references move_keyframe for channel resolution, which implies usage. However, it never states when to use this versus sibling operations (e.g., move_keyframe, remove_section, remove_sequence_track) or any preconditions, so guidance remains implied rather than explicit.

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