DaVinci Resolve MCP Server

resolve_clear_transcription

Delete transcription for one clip or an entire folder tree, including nested subfolders, to clear speech-to-text results.

Instructions

Delete transcription for one clip, or the current/specified folder AND nested folders.

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

Input Schema

Name	Required	Description	Default
`clip_name`	No
`folder_path`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.0Sep 22, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the operation is destructive ('Delete') and highlights the recursive scope ('AND nested folders'), which is valuable. However, it does not state irreversibility, required project context, or what happens when both clip_name and folder_path are supplied.

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?

A single sentence that front-loads the action and scope with no filler. Every phrase contributes meaning, and the alternative scopes are clearly separated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is not complete enough for a destructive tool with no output schema and no annotations. It does not clarify parameter priority, the meaning of 'current' folder, prerequisites like a loaded project, or what result the agent should expect. This ambiguity could lead to incorrect invocation when both parameters are relevant.

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%, so the description must compensate. It adds meaning by connecting 'one clip' to clip_name and 'current/specified folder AND nested folders' to folder_path. Yet it leaves ambiguity about which parameter takes precedence, what 'current' means, and whether the two parameters can be used together.

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 a specific verb and resource ('Delete transcription') and clearly scopes the action to 'one clip' or a folder including nested folders. It is immediately distinguishable from siblings like resolve_clear_audio_classification and resolve_get_transcript because it targets transcription deletion specifically.

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 explicit guidance on when to use this tool versus alternatives such as resolve_clear_audio_classification or when to prefer folder-scoped vs clip-scoped deletion. The description implies the use case but does not state exclusions, alternatives, or prerequisites.

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

Deploy Server