Skip to main content
Glama

media_pool

List bins and clips in DaVinci Resolve's media pool, search clip names, and optionally include properties, metadata, and markers for detailed inspection.

Instructions

List bins and clips in the media pool (from bin, default root). search filters clip names (case-insensitive substring); detail=true adds all clip properties, metadata and markers.

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": "media_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
binNo
limitNo
detailNo
searchNo
recursiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are present, so the description carries the full load. It usefully discloses that search is case-insensitive substring matching and that detail=true expands the payload with properties, metadata and markers, but it omits two behaviors an agent would hit immediately: recursive defaults to true (so sub-bins are traversed) and limit defaults to 300, implying silent truncation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the operation and scope, then parameter semantics in a compact clause. No filler, no restatement of the tool name.

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 and no annotations, the description should clarify what a listing entry looks like and how truncation/traversal behave. It covers the shape of the expansion via detail=true but leaves the default limit of 300 and recursive=true unexplained, which materially affects interpretation of results.

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 description coverage is 0%, so all five parameters needed documenting and the description covers only three (bin, search, detail). The limit and recursive parameters are completely undocumented in both schema and prose, leaving the caller to guess at truncation and subtree traversal.

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?

Specific verb plus resource ("List bins and clips in the media pool") with an explicit scope anchor ("from `bin`, default root"). An agent can tell this is the read/browse entry point for the media pool, though it does not name a sibling to contrast with (bin_manage, clip_info, media_select).

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 only implied: browse the media pool, optionally scoping to a bin. There is no statement of when to prefer this over bin_manage, clip_info, or media_select, and no note on when detail=true is worth the payload cost versus a shallow listing.

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