Skip to main content
Glama

Inspect Timeline Snapshot

inspect_timeline_snapshot

Captures an exact Premiere CEP sequence as a canonical, tick-accurate snapshot with bounded clips, completeness flags, and optional JSON output for reliable timeline inspection.

Instructions

Inspect one exact CEP sequence into version1 canonical snapshot preserving raw tick strings, source/link identities, bounded clips and explicit unknown fields. Track targeted/muted come from the documented track DOM; sync_locked comes from the experimental QE DOM only when this is the active sequence and stays null otherwise. Host missing lock/effect/transition/marker state remains incomplete; this inspection never implies atomic host state. Re-query from zero after change or truncation. With output_path inside an approved private workspace the snapshot is written to a .json file (sha256 reported); its parent must satisfy bridge ownership/ancestor protections (0700 on POSIX), and failures can leave an empty reservation and return_content:false keeps the clips out of the reply.

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": {
      "sequence_id": "<sequence_id>"
    },
    "name": "inspect_timeline_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_clipsNoBounded returned clips, default1000. Missing tail is explicitly incomplete.
output_pathNoOptional absolute .json path to write the snapshot to. Requires approved_workspace_path; the file must not already exist. Parent must be private and ownership-verified; failed inspection can leave an empty reservation. When omitted the snapshot is returned inline.
sequence_idYesExact host sequence ID; names are rejected.
return_contentNoInclude the full snapshot (as data.snapshot) in the result (default true). With output_path, false returns only identity, revision, counts, completeness, pagination, sha256 and path, which keeps large snapshots out of the conversation.
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
expected_revisionNoOptional exact revision; changed state requires restart.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.
approved_workspace_pathNoAbsolute existing directory that must contain output_path. Required with output_path.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A3.6/5.0
Behavior4/5

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

Substantial disclosure beyond the annotations: targeted/muted come from the documented track DOM while sync_locked comes from the experimental QE DOM only for the active sequence and is otherwise null, host state may remain incomplete, and the inspection never implies atomic host state. It also explains the write side effect (a .json file with sha256, parent ownership/0700 constraints, possible empty reservation), which reconciles with readOnlyHint=false. It does not discuss permissions or concurrency limits beyond that.

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?

The opening sentence is front-loaded and states the core purpose, but the remaining text is a dense run-on of jargon-dense clauses (DOM provenance, ownership protections, empty reservations) with no separation between output behavior and incompleteness semantics. Nearly every sentence carries content, but the lack of structure hurts scanability.

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 9-parameter tool with nested expected_* guards, an output schema, and annotations, the description covers the essential behavioral envelope: DOM provenance caveats, incompleteness, non-atomicity, and file-write failure modes. Return values are covered by the output schema, so the remaining gaps (auth/permission requirements, size limits when returning inline) are minor.

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_id, max_clips, output_path, return_content, idempotency_key and the expected_* guards in depth. The description only reinforces the output_path/return_content combination and the 'bounded clips' incompleteness semantics, adding little meaning beyond the structured fields.

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?

The description names a specific verb and resource ('Inspect one exact CEP sequence into version1 canonical snapshot') and enumerates what is preserved (raw tick strings, source/link identities, bounded clips, explicit unknown fields). It is clearly distinguishable from summary or export siblings, though it never names an alternative.

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?

Implicit usage context is present: 'Re-query from zero after change or truncation' and the note that missing host lock/effect/transition/marker state leaves the result incomplete. However, there is no explicit statement of when to pick this over preview_otio_snapshot_export, get_timeline_summary, or audit_timeline_health, so the agent must infer 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