Skip to main content
Glama

Preview Mogrt Premiere Handoff

preview_mogrt_premiere_handoff
Read-onlyIdempotent

Preview a contained MOGRT import into one named disposable Premiere verification sequence and empty video track, without contacting Premiere or altering a sequence.

Instructions

Preview a contained MOGRT import into one explicitly named disposable Premiere verification sequence and empty video track. It does not contact Premiere or alter a sequence.

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": {
      "approved_workspace_path": "<approved_workspace_path>",
      "mogrt_path": "<mogrt_path>",
      "sequence_id": "<sequence_id>",
      "disposable_sequence_name": "<disposable_sequence_name>"
    },
    "name": "preview_mogrt_premiere_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
mogrt_pathYesExisting workspace-contained MOGRT artifact.
sequence_idYesExact Premiere sequence identifier to recheck before import.
start_secondsNoInsertion start time in seconds; defaults to 0.
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.
audio_track_indexNoAudio track index passed to Premiere; defaults to 0.
video_track_indexNoEmpty video track index for the imported MOGRT; defaults to 0.
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_pathYesAbsolute operator-approved workspace root.
disposable_sequence_nameYesMust begin with 'MOGRT Verify - '.

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is structured data. The description usefully adds that no Premiere contact occurs and no sequence is altered, and that the sequence must be a disposable verification one, but says nothing about what the preview emits, how the idempotency key behaves, or how expected_cep_target guards are evaluated.

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?

Two short sentences, front-loaded with the core action and followed immediately by the non-mutation guarantee. No filler and no repetition of schema detail.

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

Completeness3/5

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

For a 10-parameter tool with nested CEP guard objects and an idempotency contract, the description is quite thin: it does not explain what the preview produces, how it relates to the apply step, or that the guard arguments are validated pre-generation. The output schema and rich parameter descriptions carry much of the load, but the definition leaves an agent guessing about the preview/apply workflow.

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 every parameter is already documented in the schema, giving a baseline of 3. The description adds only mild reinforcement ('explicitly named disposable', 'empty video track') that overlaps with the existing disposable_sequence_name prefix rule and video_track_index description.

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?

States a specific verb-and-resource pair: preview a contained MOGRT import into one named disposable Premiere verification sequence and empty video track. It clearly marks the operation as a preview and non-mutating, which separates it in spirit from apply_mogrt_premiere_handoff, though that sibling is never named.

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 'disposable Premiere verification sequence' and 'does not contact Premiere' imply a dry-run/verification use case, but there is no explicit when-to-use statement, no pointer to apply_mogrt_premiere_handoff as the follow-up, and no stated prerequisites for choosing this over the apply variant.

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