Import audio files into DaVinci Resolve directly, or provide a YouTube URL to download and extract high-fidelity 48kHz WAV audio automatically.
Imports audio file into DaVinci Resolve. If given a YouTube URL, automatically downloads and extracts high-fidelity 48kHz WAV audio first.
| Name | Required | Description | Default |
|---|---|---|---|
| path_or_url | Yes | ||
| destination_folder | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description reveals the side effect of downloading and extracting audio for YouTube URLs, but it does not clarify whether the tool is read-only or mutates the project state (e.g., adding media to the timeline). Without annotations, the description carries the full burden but only partially addresses this.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, consisting of two short sentences that convey the essential information without any unnecessary words. The structure is efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the wide range of sibling tools (e.g., import_media, smart_ingest, analyze_audio_beats), the description does not differentiate this tool from alternatives or mention when it is the appropriate choice. It also omits any information about return values or error handling, but the core function is clear enough for basic use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description implicitly refers to path_or_url as either a file path or YouTube URL, but it does not explicitly explain either parameter. The destination_folder parameter is not mentioned at all, leaving its role unexplained. Since the schema provides no descriptions, the tool description fails to adequately document the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's primary function: importing an audio file into DaVinci Resolve. It also explicitly covers the special case of YouTube URLs, which includes downloading and extracting 48kHz WAV audio, leaving no ambiguity about the tool's purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides some usage guidance by mentioning the YouTube URL scenario, but it lacks explicit instructions on when to choose this tool over siblings like import_media or smart_ingest. No prerequisites or context are given beyond the core function.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.