Skip to main content
Glama

Validate Project For Export

validate_project_for_export
Read-onlyIdempotent

Run a non-mutating export preflight on a sequence to catch blocking offline media, empty timelines, inaccessible preset or output paths, and optional gaps before queuing an export.

Instructions

Run a non-mutating export preflight for an active or named sequence. It reports blocking offline media, empty timelines, inaccessible preset/output paths, duration, and optional timeline gaps without queuing an export. readyForExport means these preflight checks passed; it does not test exporter initialization, encoder availability, or whether the host can render. Require an actual output file from export_sequence and verify_delivery_file before claiming delivery.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "validate_project_for_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
gap_limitNoMaximum per-track gaps to return when per_track_gaps is true (default 200).
check_gapsNoReport gaps on populated tracks as warnings (defaults to true).
gap_offsetNoZero-based offset into the optional per-track gap list (default 0).
output_pathNoOptional intended delivery path; its parent folder is checked.
preset_pathNoOptional .epr preset path to check.
sequence_idNoSequence ID or name. Defaults to the active sequence.
per_track_gapsNoInclude the per-track gap list in a bounded page (default false); composite black/dead-air checks remain available without it.
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_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.
require_non_empty_timelineNoTreat an empty sequence as a blocking error (defaults to true).

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

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/destructiveHint/idempotentHint, but the description adds real substance beyond them: it says nothing is queued, defines what readyForExport does and does not certify, and warns against over-claiming delivery. This is exactly the failure-mode disclosure an agent needs before trusting a green preflight.

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?

Three tight sentences, front-loaded with purpose, then the limitation of readyForExport, then the correct downstream workflow. Every sentence carries load; the pessimistic warning about claiming delivery is the highest-value line and is placed last for emphasis without padding.

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 an 11-parameter tool with nested CEP guard objects and an output schema, the description covers purpose, non-mutation, result meaning, and failure limits adequately, and the output schema carries return-structure detail. It does not explain the idempotency_key or expected_cep_target guard parameters at all, but those are fully specified in the schema, so nothing essential 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 coverage is 100%, so every parameter (gap_limit, check_gaps, per_track_gaps, gap_offset, preset_path, output_path, sequence_id, and the idempotency/CEP guards) is already documented in the schema. The description loosely references optional timeline gaps and preset/output path checks but adds no formats, defaults, or semantics beyond the schema text. 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?

Names a specific verb+resource ("non-mutating export preflight") plus scope ("active or named sequence") and enumerates exactly what it reports: blocking offline media, empty timelines, inaccessible preset/output paths, duration, gaps. It is clearly separable from export_sequence and verify_delivery_file, which are named as the actual delivery path.

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?

States when to use it (preflight before export) and when it is insufficient ("Require an actual output file from export_sequence and verify_delivery_file before claiming delivery"). The explicit carve-out that it does not test exporter initialization, encoder availability, or host rendering is a strong use-boundary. It stops short of naming a sibling preflight alternative such as validate_export_preset, so it is not a full when/when-not routing statement.

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