Skip to main content
Glama

media_import

Import files or folders into a DaVinci Resolve media pool bin, creating the bin if missing. Supports glob patterns, recursive folder import, and numbered image sequences.

Instructions

Import files or folders into the media pool (into bin, e.g. 'Footage/Day1'; created if missing). Paths may contain globs ('~/Footage/*.mov'). Folders import their media (recursive=true walks sub-folders). sequence=true imports numbered images as one image sequence (pass one frame or a %04d pattern).

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": {
      "paths": "<paths>"
    },
    "name": "media_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
binNo
pathsYes
sequenceNo
recursiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful side effects: the target bin is created if missing, globs are expanded, and recursive=true walks sub-folders. It is silent on duplicate/existing-media handling, permission requirements, and error behavior for invalid paths, which matters for a mutation tool with zero annotation coverage.

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?

Front-loaded with the core action, then three compact sentences covering bin, paths, and the sequence/recursive flags. Dense but every clause carries information; the parenthetical examples are the only mildly noisy element.

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

Completeness4/5

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

For a 4-parameter import tool with no annotations and no output schema, the definition covers the target location, path syntax, and both flag semantics adequately. The main remaining gap is whether re-importing existing media duplicates or replaces, which the description never addresses.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the prose must compensate, and it largely does: bin is explained with an example path and create-if-missing semantics, paths explicitly accept globs, sequence is tied to numbered images and the %04d pattern, and recursive is tied to sub-folder walking. All four parameters gain meaning beyond the bare schema.

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?

The description opens with a specific verb+resource: import files or folders into the media pool. The 'media pool' target distinguishes it from unrelated siblings at a high level, though it never explicitly contrasts with project_import or timeline_import, so an agent must infer the scope difference.

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?

Usage context is implied by the media-pool framing and the notes about folders, globs, and sequences, but there is no explicit when-to-use or when-not-to-use statement and no named alternative for importing into a project or timeline instead.

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