Skip to main content
Glama

audio_mapping

Get or set audio channel mapping for a media pool clip or timeline clip, matching Resolve's Clip Attributes. Routes audio tracks correctly by applying a track mapping.

Instructions

Get or set audio channel mapping (JSON as in Resolve's Clip Attributes) for a media pool clip, or for a timeline clip with timeline_clip=true. Set only needs {"track_mapping": {...}}.

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": {
      "target": "<target>"
    },
    "name": "audio_mapping"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
mappingNo
timeline_clipNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the meaningful dual read/write nature and pins the mapping format to Resolve's Clip Attributes JSON, which prevents guesswork. It omits whether a set overwrites the entire mapping, what invalid JSON does, permission needs, and the return shape.

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 tight sentences, dual-mode purpose front-loaded, the timeline variant stated immediately after. The trailing clause on set payload shape is slightly compressed but earns its place.

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?

With no annotations, no output schema, and zero schema-level parameter documentation, an agent still lacks the target identifier format and what a get returns. Adequate for invoking in the common case but not fully self-sufficient.

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 0% with three parameters, so the description must compensate; it partly does by explaining timeline_clip's role and the shape of mapping for writes. However, `target` is left unspecified—no indication whether it is an id, name, or path—and mapping's read-side content is undefined.

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 concrete verb pair (get/set) and resource (audio channel mapping) plus the two target scopes (media pool clip vs. timeline clip). This is clearly distinct from siblings like audio_insert or audio_normalize, though it never names an alternative to route against.

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?

Gives one explicit routing rule: use timeline_clip=true for timeline clips. It also notes that setting only needs {"track_mapping": {...}}. It does not say when to omit mapping versus supply it, nor how it relates to neighboring audio tools.

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