Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

remove_sequence_folder

DestructiveIdempotent

Remove a Sequencer outliner folder from a Level Sequence's movie scene inside an undo transaction and save the sequence to finalize the change.

Instructions

Remove a Sequencer outliner folder (root, or a named child of parent_folder) from a Level Sequence's movie scene, inside an undo transaction, and save the sequence; success requires the save. Inverse of add_sequence_folder; idempotent by name: an absent folder succeeds with already_absent true and saved false (nothing is written).

Returns: { sequence_path: string, folder_name: string, parent_folder: string, removed: bool, already_absent: bool, root_folder_count: int, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_nameYesName of the folder to remove.
parent_folderNoOptional name of the parent folder (searched recursively); if given, the child folder named folder_name is removed from it instead of a root folder.
sequence_nameNoAlias for sequence_path.
sequence_pathNoAsset path OR bare asset name of the target Level Sequence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / required
      Previous value: -[
-  "sequence_path",
-  "folder_name"
-]New value: +[
+  "folder_name"
+]
  2. First observedv1.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint, idempotentHint, and readOnlyHint=false, but the description adds substantial context beyond them: the operation runs inside an undo transaction, success is contingent on the save, and an absent folder returns already_absent=true with saved=false and writes nothing. It also discloses the save_error return path.

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?

Purpose is front-loaded in the first clause, followed by behavioral caveats and then the return shape. Despite dense semicolon usage, every clause carries distinct information (scope, transaction, save condition, absent-case behavior) with no filler.

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 separate output schema, the description inlines the return object including fields, types, and the optional save_error, and it covers the mutation semantics, transaction context, and idempotent edge case. An agent has everything needed to invoke and interpret the result.

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 all four parameters are already documented in the schema. The description restates root-vs-parent_folder behavior and folder_name semantics without adding format or syntax details the schema lacks, matching the baseline-3 expectation when structured fields do the heavy lifting.

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 (Sequencer outliner folder) with scope precision: root vs. named child of parent_folder, and explicitly names its inverse add_sequence_folder. An agent can distinguish this from siblings like remove_sequence_track or remove_section without opening a 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?

The inverse-of-add_sequence_folder framing plus the idempotency note gives clear context for when this tool applies. It does not explicitly exclude or compare against close alternatives, but no sibling overlaps this exact operation, so the guidance is sufficient without being exhaustive.

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