Skip to main content
Glama

list_clips

Read-only

Lists clips in a DaVinci Resolve media pool or bin with bin paths and selected properties, plus optional recursive search, name filtering, and result limits.

Instructions

Clips in the media pool (or in bin), with their bin path and a few properties (default: Type, File Path, Duration, FPS, Resolution, Start/End TC, Clip Color, codec, audio channels). Pass properties for others (see get_api_type('ClipProperties')), [] for none.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
binNo
limitNo
recursiveNo
propertiesNo
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context by enumerating the default returned properties and pointing to get_api_type('ClipProperties') for the full set. However, it never mentions that `recursive` defaults to true (sub-bin traversal) or that `limit` defaults to 500, both of which materially affect results.

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?

Two compact sentences with the resource scope front-loaded and the property guidance following. The nested parenthetical listing defaults is dense but every clause carries information; no filler.

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 no output schema, the description does the right thing by listing default return properties, and it directs the agent to get_api_type for the property vocabulary. It is still incomplete for a 5-parameter listing tool: recursion behavior, result limiting, and name filtering are unaddressed, and no ordering or result-size expectations are given.

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 must carry the parameter burden; it clarifies `bin` and `properties` (including the [] convention and where to look up valid values), which is real added meaning beyond the bare schema. It says nothing about `limit`, `recursive`, or `name_contains`, leaving three of five parameters undocumented anywhere.

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?

"Clips in the media pool (or in `bin`)" names the resource and scope precisely, letting an agent distinguish it from get_selected_clips and list_track_items by where the clips come from. The verb is elided ("list" is only implied by the tool name), so it stops just short of a fully self-contained statement.

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 is implied by the scope wording (media pool or a specific bin), and the note about passing `properties` or [] gives a hint on tailoring the call. There is no explicit statement of when to prefer this over siblings like get_selected_clips or list_track_items, and no 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