Skip to main content
Glama

export_clip_metadata

Exports clip metadata from DaVinci Resolve to a CSV file, covering all clips or a specified subset for reporting and analysis.

Instructions

Export clip metadata to a CSV file (all clips, or only clips).

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": {
      "path": "<path>"
    },
    "name": "export_clip_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
clipsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already state the operation is not read-only but also not destructive, so the agent knows it writes something. The description adds only that the target is a CSV file, and says nothing about whether an existing file at `path` is overwritten, whether the directory must exist, permissions, or the size/rate of large exports. For a file-writing tool with a required path argument, those gaps are significant.

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?

A single front-loaded sentence with no filler; the parenthetical is compact and informative. It is arguably over-compressed, but nothing in it is wasted.

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

Completeness3/5

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

With only two parameters and no output schema, the definition is close to adequate, but the file-writing side effects (overwrite semantics, return value/confirmation) are unaddressed. An agent knows what to call but not fully what to expect from the call.

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 coverage is 0%, so the description carries the full burden, and it does explain that `clips` narrows the export to a subset while omitting it exports everything. It does not clarify the type/identifier format expected in the `clips` array or what `path` must look like (absolute path, filename extension), leaving the schema's bare 'Path' title to do that work.

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 names a specific verb and resource ('Export clip metadata') and adds the output format ('to a CSV file'), which is clearly distinct from siblings like export_bin or export_timeline. It does not explicitly contrast itself with those siblings, but the resource is unambiguous enough that an agent can identify exactly what is written.

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?

The parenthetical '(all clips, or only `clips`)' implies when the optional parameter should be supplied, which is useful implied usage. However, it gives no context about prerequisites (e.g., an open project, destination directory), nor does it mention any alternative export tool for different scopes.

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