Skip to main content
Glama

create_cine_camera_in_sequence

Spawn a CineCameraActor in a Level Sequence, key its transform at frame 0, and bind a camera cut across the playback range.

Instructions

Creates a spawnable CineCameraActor binding, keys its transform, and binds a camera cut to it. High-value one-shot: spawnable CineCameraActor + transform track keyed at frame 0 + a camera cut spanning the playback range.

Returns: { sequence_name: string, binding_guid: string, display_name: string, class_name: string, spawnable: bool, transform_keyed: bool, camera_cut_added: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoOptional [x, y, z] world location for the camera's key at frame 0.
rotationNoPREFERRED: the OBJECT {"roll":R,"pitch":P,"yaw":Y} (any subset, absent axes are 0). The ARRAY form below is [pitch, yaw, roll] -- its index 2 is ROLL, NOT yaw, which once put a PlayerStart on its side. Optional [pitch, yaw, roll] world rotation for the camera's key at frame 0.
sequence_nameYesName of the target Level Sequence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 the write/non-idempotent/non-destructive profile, and the description adds real context beyond them: exactly what artifacts get created and that a camera cut spans the playback range. The returns block volunteering a 'saved' flag and optional 'save_error' also discloses the persistence side effect, which annotations do not convey.

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?

Purpose and the 'one-shot' framing are front-loaded, and the returns block is justified because no output schema exists. Every sentence carries information, though the prose is slightly dense and the returns list is long relative to the rest.

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?

For a mutation tool with no output schema, the description compensates by spelling out the return shape and the composite effects, which would otherwise be opaque. It stops short of stating prerequisites (e.g. that the level sequence must already exist), leaving a small gap.

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 sequence_name, location, and rotation in detail (including the array-vs-object rotation warning). The description adds no additional parameter meaning, so the baseline 3 applies.

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 names a specific verb and resource ('Creates a spawnable CineCameraActor binding') and enumerates the three composite operations performed (spawnable, transform track keyed at frame 0, camera cut). It is clearly distinguishable from siblings like add_spawnable_to_sequence or add_camera_cut because it presents itself as a one-shot that does all three.

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 phrase 'High-value one-shot' implies this is a shortcut combining several lower-level calls, which hints at when to prefer it. However, no alternative siblings are named and there is no explicit when-not guidance or prerequisite statement, leaving the agent to infer the 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