Skip to main content
Glama

import_media

Import files or folders into a DaVinci Resolve media pool bin, including image-sequence frame ranges, or route imports through Media Storage for sequence detection and start/end handling.

Instructions

Import files or folders into the media pool (into bin, default the current bin). Each item is a path, or {"path", "start", "end"} to import a frame range of an image sequence. via_media_storage=true uses Media Storage's AddItemListToMediaPool (honours its sequence detection and start/end frames).

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": {
      "items": "<items>"
    },
    "name": "import_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
binNo
itemsYes
via_media_storageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the mutation and closed-world/non-destructive profile, so the description focuses on useful extras: how frame ranges are specified and that via_media_storage delegates to AddItemListToMediaPool, inheriting its sequence detection and start/end handling. It stops short of covering failure behavior, duplicate/re-import handling, or whether existing pool items are touched.

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?

Three compact sentences with the primary action front-loaded and the mode-specific detail following. No filler, though the parenthetical about the default bin interrupts the main sentence slightly.

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 3-parameter mutation tool with no output schema and annotations covering safety, the definition supplies the essential usage information, especially the polymorphic items format that the schema cannot express. The remaining gap is destination-value semantics for 'bin' and any note on how results or failures surface.

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?

With 0% schema description coverage, the description must carry the burden. It does well for 'items' (a path string or a {path,start,end} object for image sequences) and explains 'via_media_storage', but 'bin' is only said to default to the current bin — it never clarifies whether the value is a bin name, path, or ID, and the schema leaves it as a bare nullable string.

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 states a specific verb and resource ('Import files or folders into the media pool') and clarifies the destination default (current bin). It does not distinguish itself from sibling tools with similar names such as import_bin or import_into_timeline, so the agent must infer the boundary.

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?

It implies default destination behavior and explains the two import modes (direct vs via_media_storage), which gives some context for selection. However, it never states when to prefer this tool over import_bin, import_into_timeline, or clone_media, and gives no prerequisites or exclusions.

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