premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Create Bars And Tone

create_bars_and_tone

Creates a Bars and Tone synthetic media item in your Premiere Pro project for leader or calibration use, optionally placing it in a specific bin and returning its name, nodeId, and treePath.

Instructions

Create a Bars and Tone synthetic media item in the project (useful for leader/calibration). Returns the created item's name, nodeId, and treePath, found by reading the project back.

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": "create_bars_and_tone"
  }
}

Input Schema

Name	Required	Description
`name`	No	Name for the bars and tone item (default: 'Bars and Tone')
`width`	No	Frame width in pixels (default: 1920)
`bin_id`	No	Optional destination bin: node ID, slash-separated bin path from the project root, or bin name. The bin is resolved before anything is created; the item is moved there and its location read back.
`height`	No	Frame height in pixels (default: 1080)
`timebase`	No	Timebase as ticks-per-second string (default uses sequence timebase)
`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.
`audio_sample_rate`	No	Audio sample rate in Hz (default: 48000)
`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.
`pixel_aspect_numerator`	No	Pixel aspect ratio numerator (default: 1)
`pixel_aspect_denominator`	No	Pixel aspect ratio denominator (default: 1)

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

A4/5.0

Behavior4/5

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

Annotations only declare the safety profile (readOnly=false, destructive=false, idempotentHint=false), while the description adds real behavioral value: the tool reads the project back to resolve the created item and returns name, nodeId, and treePath. It does not note that a destination bin is resolved before creation or that an idempotency key can be supplied, but those live in the schema rather than being contradicted.

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 tight sentences: the action and its purpose come first, the return shape second. Nothing is redundant and every clause earns its place.

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 an output schema present, the description need not explain return values in depth, and it still names the key fields returned. For an 11-parameter creation tool whose parameters are fully documented in the schema, this is close to complete, with only the absence of guidance on when to choose this over other creation tools as a minor gap.

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 all 11 parameters, including the nested expected_cep_target and expected_project_path guards, are thoroughly documented in the schema. The description adds no parameter-level meaning, 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?

States a specific verb and resource ('Create a Bars and Tone synthetic media item in the project') and adds the intent ('useful for leader/calibration'), which makes it unmistakably distinct from the other create_* siblings such as create_bin, create_sequence, or create_subclip.

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?

The parenthetical 'useful for leader/calibration' gives an implied usage context, so an agent can infer when this tool is appropriate. However, there is no explicit when-not guidance, no mention of prerequisites, and no routing to alternatives for other kinds of synthetic media.

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

Deploy Server