Skip to main content
Glama
Sign In
DaVinci Resolve MCP Server

DaVinci Resolve MCP Server

by angelOnly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_audio_volume

Set the audio volume of a clip in a DaVinci Resolve timeline by specifying its name and desired volume level.

Instructions

Set the audio volume of a timeline clip by name.

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": {
      "clip_name": "<clip_name>",
      "volume": "<volume>"
    },
    "name": "set_audio_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeYes
clip_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the obvious mutation. It does not mention volume units, error behavior, or scope of effect (e.g., whether it affects linked clips).

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?

The description is a single, front-loaded sentence with no filler, earning a perfect score for conciseness.

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?

Although the tool is simple, the description lacks usage guidelines and parameter details like volume units. The presence of sibling tools like set_track_volume makes this gap notable, but the core purpose is clear; overall it is minimally adequate.

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 description adds the clarification that the clip is identified 'by name' for the clip_name parameter, which is useful. However, it does not specify units or range for the volume parameter, and schema coverage is 0%.

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?

The description uses the specific verb 'set' and identifies the resource as 'audio volume of a timeline clip by name.' It clearly distinguishes this tool from sibling set_track_volume, making the purpose unmistakable.

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?

The description provides no guidance on when to use this tool versus alternatives like set_track_volume or set_clip_property. It only states what it does, leaving the agent to infer appropriate usage context.

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