Premiere Pro MCP Server

Set Project Item Audio Channel Mapping

set_project_item_audio_channel_mapping

Assign a project item's output audio channel to a specific source channel. Use this mapping to route audio correctly within Premiere Pro.

Instructions

Map one output audio channel of a project item to a source channel using Premiere's documented AudioChannelMapping API.

Input Schema

TableJSON Schema

Name	Required	Description
`item_id`	Yes	Project item node ID or exact name
`channel_index`	Yes	Zero-based output channel index to configure
`source_channel_index`	Yes	Zero-based source channel index to map

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.14.4Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}

Addedv1.4.0Jul 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The annotations are all false hints, so they do not establish a meaningful safety profile, and the description must carry the burden. It does not disclose whether repeated calls replace or append mappings, whether invalid channel indices error, whether the change affects all instances of the item, or whether the operation is reversible. 'Map' implies a configuration mutation but nothing about consequences.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with the action verb and resource up front, making it easy to scan. The reference to 'Premiere's documented AudioChannelMapping API' adds a little specificity but is not redundant enough to hurt clarity.

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?

For a three-parameter tool with fully described schema fields, the essential call shape is understandable. However, an agent still lacks guidance on when to use this versus other audio tools and what side effects to expect, so the description is minimally viable but not complete.

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?

The input schema already documents all three parameters clearly, including 'Zero-based output channel index to configure' and 'Zero-based source channel index to map,' so schema description coverage is 100%. The description adds conceptual direction but no additional parameter-level detail, matching the baseline for fully schema-documented 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 description names a specific operation ('Map one output audio channel... to a source channel') and a specific resource ('a project item' via the AudioChannelMapping API), so an agent can tell it performs channel mapping. It does not explicitly contrast itself with sibling tools, but the resource and verb are distinctive enough among the audio-related siblings.

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 guidance about when to use this tool instead of related audio tools like adjust_audio_levels, apply_audio_effect, or set_sequence_audio_settings. No prerequisites, preconditions, or exclusions are given; the only contextual hint is the tool name and the generic 'map' operation.

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

Deploy Server