Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read Video Scopes

read_video_scopes

Extracts waveform and RGB parade percentiles, saturation, and near-black/near-white RGB occupancy from one bounded decoded local-media frame for sampled read-only video analysis.

Instructions

Read waveform percentiles, RGB parade percentiles, saturation, and near-black/near-white RGB occupancy from one bounded decoded local-media frame. Read-only; this is a sampled analytical proxy, not Premiere's rendered scopes.

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": {
      "media_path": "<media_path>"
    },
    "name": "read_video_scopes"
  }
}

Input Schema

NameRequiredDescriptionDefault
use_cacheNoOpt in to bounded process-memory caching keyed by source path/identity, media content SHA-256, exact options, revision, and analysis version. Files over 256 MiB analyze uncached. Default false.
media_pathYesExisting local video file
time_secondsNoSource-relative frame time from 0 through 86400 seconds (default: 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.
analysis_revisionNoOptional project/timeline revision to isolate otherwise-identical analysis inputs.
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
Behavior3/5

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

The description adds real context beyond annotations: it states the operation is read-only, operates on exactly one bounded decoded frame, and is a sampled proxy rather than ground-truth rendered scopes. This discloses the key accuracy limitation an agent needs. The only tension is that annotations declare readOnlyHint=false, but that is the MCP conservative default (read-only not asserted) rather than a positive claim of mutation, and it is consistent with destructiveHint=false and the schema's own 'Read-only invocations are never deduplicated' language, so it is not a true contradiction.

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 sentences, no filler, with the capability listed first and the caveat second. Every clause carries information an agent would otherwise have to guess.

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?

With a full output schema, detailed annotations, and 100% parameter coverage, the description only needs to establish purpose and the sampling caveat, which it does. Minor gap: it does not clarify that this is a local-only tool that never inspects Premiere, despite the schema carrying CEP project/sequence guard fields that could mislead an agent into thinking host identity is required.

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% and the seven parameters, including the nested expected_cep_target and idempotency_key, are documented in the schema itself. The description contributes nothing parameter-specific beyond 'one bounded decoded local-media frame', so the baseline of 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?

The description names a specific verb and resource ('Read waveform percentiles, RGB parade percentiles, saturation, and near-black/near-white RGB occupancy') and constrains the input ('from one bounded decoded local-media frame'). The closing contrast, 'not Premiere's rendered scopes', separates it from the rendered-scopes sibling without requiring the agent to open either schema.

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?

The phrase 'sampled analytical proxy, not Premiere's rendered scopes' gives a clear selection rule: use this for fast sampled analysis of a local media file, not for authoritative rendered-scope inspection. It stops short of an explicit 'use inspect_rendered_video_scopes when you need X' routing statement, and gives no preconditions (supported codecs, cost of decoding).

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