Imports media files from absolute paths into the DaVinci Resolve Media Pool, enabling AI agents and CLI tools to add project assets for editing.
Import media files (absolute paths) into the Media Pool.
| Name | Required | Description | Default |
|---|---|---|---|
| paths | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a write operation to the Media Pool but does not disclose side effects, duplicate handling, supported formats, permissions, or failure behavior.
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 a single efficient sentence with the key operation and path constraint front-loaded. There is no wasted text, though the brevity leaves important details unstated.
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?
For an import tool with no annotations and no output schema, the definition is too thin. An agent lacks guidance on prerequisites, supported media types, duplicate handling, and what the import operation returns or changes.
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?
Schema description coverage is 0%, but the description adds useful meaning by stating that paths must be absolute media file paths. It does not explain the array nature, multiple-file behavior, or supported file types beyond that.
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 states a specific verb and resource: import media files into the Media Pool. This clearly identifies the operation, though it does not explicitly differentiate from any sibling tool because no direct import alternative exists.
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 gives only a parenthetical note that paths must be absolute, with no guidance on when to use this tool versus alternatives. It does not mention prerequisites such as having a project open or a target bin selected.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.