Skip to main content
Glama

Add Marker To Project Item

add_marker_to_project_item

Add a named marker to a Premiere Pro project item or source clip at a specified time, with optional type, comment, color, and duration.

Instructions

Add a marker to a project item (source clip marker). EXPERIMENTAL QE: records an observed marker boundary for guarded Undo/Redo; crossing it is refused by default, and unreadable history records unknown protection. This boundary does not verify native marker reversal. Marker start and end storage are compared at exact integer ticks; unsupported time writes remain unverified with the created marker identity when available.

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": {
      "item_id": "<item_id>",
      "time_seconds": "<time_seconds>"
    },
    "name": "add_marker_to_project_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMarker name
typeNoMarker type (default: Comment)
item_idYesNode ID or name of the project item, or the sequence ID of a sequence
commentsNoMarker comments
color_indexNoColor label index (0-7)
time_secondsYesTime in seconds for the marker
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.
duration_secondsNoDuration of the marker in seconds (0 for point marker)
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

B3.1/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds genuine behavioral context beyond that — an observed marker boundary is recorded, crossing it is refused by default, and unreadable history is treated as unknown protection — but the undefined abbreviation 'QE' and the caveat that native marker reversal is not verified leave the agent guessing what 'crossing' actually means in practice.

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 purpose is front-loaded in the first sentence, which is good, but the remaining three sentences are dense, run-on guard prose about undo boundaries and tick comparison that an agent must parse before acting. Nothing is strictly redundant, yet the density and undefined jargon work against quick comprehension.

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?

With an output schema present, the description needn't explain return values, and the input schema carries the parameter detail. What remains thin is operational framing for a mutation with a guard layer: it never states what a refusal looks like to the caller, what 'unsupported time writes remain unverified' means for the created marker, or how this interacts with the sibling marker tools.

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 all ten parameters including the nested expected_cep_target and idempotency_key are already documented; baseline 3 applies. The description does add a small amount beyond the schema by stating that marker start and end storage are compared at exact integer ticks, implying sub-second precision matters for the time parameters.

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 first sentence gives a specific verb and resource ("Add a marker to a project item") and narrows the scope with "(source clip marker)", which implicitly separates it from the sequence-level add_marker sibling. It does not name that sibling explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says when to pick this over add_marker, update_marker, or delete_marker, and no prerequisites (project open, item selected, Undo history readable) are given as conditions for choosing the tool. The 'EXPERIMENTAL QE' sentence describes the guard but not the decision 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