Skip to main content
Glama

Set Project Item Audio Channel Mapping

set_project_item_audio_channel_mapping

Maps a project item's output audio channel to a selected source channel, enabling per-channel audio routing configuration in Adobe Premiere Pro.

Instructions

Request one output-to-source audio channel mapping using the documented API. Per-channel mapping has no documented getter, so accepted writes remain committed_unverified.

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>",
      "channel_index": "<channel_index>",
      "source_channel_index": "<source_channel_index>"
    },
    "name": "set_project_item_audio_channel_mapping"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesProject item node ID or exact name, or the sequence ID of a sequence
channel_indexYesZero-based output channel index to configure
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.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
source_channel_indexYesZero-based source channel index to map
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.4/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-open-world write and — notably — idempotentHint=false, despite the schema offering an idempotency_key. The description adds genuinely valuable behavior beyond that: since there is no documented getter for per-channel mappings, an accepted write stays 'committed_unverified,' which tells the agent it cannot confirm the result and should not assume success is inspectable.

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?

Two sentences, no padding, and the most decision-relevant fact (unverifiable write) is placed where it will be read. 'Request ... using the documented API' is slightly soft wording for a mutation, but nothing needs trimming.

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?

The write-verification caveat is well covered, and the output schema plus the richly documented parameters carry most of the remaining burden. What is missing is the operational envelope: whether the target item must be a sequence, whether the CEP backend is required (the schema's expected_cep_target says UXP refuses it), and how out-of-range channel indices behave.

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 the schema already explains item_id, channel_index, source_channel_index and the idempotency/CEP guard objects. The description reinforces the output-to-source direction of the two channel indices, which is a small but real disambiguation, otherwise it adds nothing the schema lacks.

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 states a specific verb and resource: 'Request one output-to-source audio channel mapping,' which tells an agent exactly what is being written and in which direction (output channel -> source channel). It does not, however, distinguish this from neighboring audio tools such as set_sequence_audio_settings, so the agent cannot route between them on the description alone.

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, no prerequisites (e.g. that the item must be a sequence or that the backend must be CEP), and no exclusions pointing to sibling tools. 'Using the documented API' is a reference to external documentation, not usable selection guidance.

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