Skip to main content
Glama

get_media_pool_tree

Read-only

Retrieves the media pool bin hierarchy with clip counts and optional clips, and returns the current bin, so you can inspect and navigate project media in DaVinci Resolve.

Instructions

Bin hierarchy of the media pool (from the root or bin), with clip counts and optionally the clips. Also returns the current bin.

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

Input Schema

NameRequiredDescriptionDefault
binNo
depthNo
include_clipsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 useful behavior beyond that: clip counts are included, clips are optional, and the current bin is returned as a side effect. It does not disclose what happens when the hierarchy exceeds the traversal depth, which is the main behavioral risk here.

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 short sentences, front-loaded with the resource and scope, with no filler. The final sentence about the current bin is slightly tacked on but still informative.

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?

For a three-parameter read tool with no output schema, the definition covers the intent and the main flag but leaves the depth constraint and the shape of the returned tree undocumented. An agent could call it correctly at defaults but would be guessing on deep or truncated trees.

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 and only partially does. It explains `bin` (traversal root) and `include_clips` (include clips in results), but never mentions `depth`, its default of 8, or how truncation at that limit is reported.

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 resource (the media pool bin hierarchy) and states what is returned: clip counts, optionally the clips, and the current bin. An agent can tell this apart from single-item siblings like get_clip or get_item. It lacks an explicit verb, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of when to use include_clips versus fetching clips individually via get_clip, and no note on how deep a traversal is appropriate. Usage is only implied by the phrase 'Bin hierarchy of the media pool'.

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