Skip to main content
Glama

Export Review Markers

export_review_markers

Export reviewed Premiere Pro markers to a new CSV or JSON file with exact ticks, timecodes, and source identity. Preserves comments safely and never overwrites existing files.

Instructions

Create a new bounded review-marker CSV or JSON from caller-reviewed marker readback. Includes exact ticks, rational rate, source/sequence identity and display timecodes with explicit start offset/drop-frame policy. CSV text escapes spreadsheet formula prefixes, quotes and newlines. Existing files are never overwritten.

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": {
      "output_path": "<output_path>",
      "format": "<format>",
      "target": "<target>",
      "rate": "<rate>",
      "markers": "<markers>"
    },
    "name": "export_review_markers"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYesExact rational frames per second; e.g. 30000/1001.
formatYesOutput serialization.
targetYesExact reviewed marker owner
markersYesReviewed marker readback; empty sequences still emit CSV headers.
drop_frameNoUse drop-frame timecode only for 30000/1001 or 60000/1001; default false.
output_pathYesAbsolute caller-selected local file path. Referenced media is never opened automatically.
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.

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/5.0
Behavior4/5

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

The annotations already establish that this is not read-only and not destructive, and the description adds meaningful behavior beyond those hints: output is bounded, existing files are never overwritten, and CSV text escapes formula prefixes, quotes, and newlines. It does not cover idempotency behavior despite the schema having an idempotency_key, but the safety and file-handling traits it does disclose are valuable.

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?

The description is front-loaded with the core action and resource, followed by compact notes on included data, CSV escaping, and non-overwrite behavior. Every sentence provides useful information, and there is no filler or repetition.

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 nested mutation tool with an output schema, the description covers purpose, file safety, exact tick/rate semantics, CSV escaping, and the non-overwrite guarantee. It omits idempotency behavior and the CEP/project-path guard details, but those are fully documented in the schema and are not required to understand the tool's core function.

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 all parameters in detail, including ticks, rate, target identity, drop-frame, idempotency, and CEP guards. The description restates the major concepts such as exact ticks, rational rate, source/sequence identity, and drop-frame policy but does not add parameter-level meaning beyond what the schema provides. This is the expected baseline when the schema does 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?

The description states a specific verb and resource: create a new bounded review-marker CSV or JSON from caller-reviewed marker readback. It distinguishes this from frame/export siblings by making clear that the output is marker data in CSV/JSON form, not rendered media or project exports. An agent can identify the tool's scope without opening the schema.

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?

It implies usage after caller review by saying the input comes from 'caller-reviewed marker readback' and specifies that existing files are never overwritten. However, it does not explicitly say when to choose this over sibling export or marker-listing tools, nor does it state exclusions or preconditions beyond the reviewed readback context.

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