premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Start Local Analysis Job

start_local_analysis_job

Start one allowlisted read-only local media analysis as a bounded, cancellable process job for stream, transient, motion, scope, interlacing, or active-picture checks.

Instructions

Start one allowlisted read-only local media analysis as a bounded cancellable process job. Native Premiere jobs are never cancelled by this tool.

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": {
      "tool_name": "<tool_name>",
      "arguments": "<arguments>"
    },
    "name": "start_local_analysis_job"
  }
}

Input Schema

Name	Required	Description
`arguments`	Yes	Exact analysis arguments, schema and authority checked before worker dispatch.
`tool_name`	Yes	Supported local analysis worker.
`idempotency_key`	No	Optional 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_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional 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

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present 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.

First observedv1.30.0Nov 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=false; the description adds real value by disclosing that the job is bounded, cancellable, and confined to allowlisted read-only local media analyses. It does not explain what 'bounded' means (timeout, resource caps), what happens on cancellation, or how the job's lifecycle is observed, which is the gap an agent most needs filled for an asynchronous job starter.

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 with no filler; the core scope ('allowlisted read-only local media analysis ... bounded cancellable process job') is front-loaded and the exclusion is stated compactly.

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 rich input schema, an output schema, and full annotation coverage, the description only needs to frame the job model, which it does. The remaining shortfall is the absence of any pointer to how the started job is tracked or cancelled (e.g., a status/polling sibling) for an asynchronous tool whose whole purpose is deferred execution.

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 includes the allowlisted worker enum plus a detailed idempotency_key explanation, so the schema carries the parameter burden. The description adds nothing about tool_name, arguments, or the CEP guard parameters, so baseline 3 applies.

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 object ('Start one allowlisted read-only local media analysis as a bounded cancellable process job') and scopes it against native Premiere jobs. It does not, however, distinguish itself from sibling analysis tools like analyze_video_interlacing or analyze_loudness, so the agent must infer that this is the job-based variant of those analyses.

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?

Usage is only implied: 'bounded cancellable process job' suggests long-running work that should be tracked asynchronously, and the closing sentence excludes Premiere-native job cancellation. There is no explicit when-to-use-this-vs-alternative statement and no guidance on polling the resulting job.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server