Skip to main content
Glama

get_node_graph

Read-only

Retrieves the DaVinci Resolve node graph for an item, timeline, or group target, returning node indexes, labels, LUTs, cache modes, and applied tools.

Instructions

Nodes of a node graph: index, label, LUT, cache mode and the tools used in each node. target: 'item:' (clip grade, optional layer), 'timeline' / 'timeline:' or 'group::pre' / 'group::post'.

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": {
      "target": "<target>"
    },
    "name": "get_node_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNo
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the safety profile is covered. The description adds value by listing the fields each node carries, acting as a lightweight return-value sketch in the absence of an output schema, but says nothing about structure (per-node collections), ordering, or failure behavior for invalid targets.

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 no filler, and the returned-content summary is front-loaded before the target grammar. The telegraphic phrasing is slightly dense but never wasteful.

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 two-parameter read tool with no output schema, the description covers target grammar well but leaves layer semantics and the shape of the returned node collection underspecified. Adequate to call it, not quite enough to predict exactly what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it largely does: it spells out the four accepted target grammars ('item:<uid>', 'timeline', 'timeline:<id>', 'group:<name>:pre/post'). The layer parameter is only alluded to via '(clip grade, optional layer)', leaving its meaning and interaction with target unclear.

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 the resource and then enumerates the per-node fields returned (index, label, LUT, cache mode, tools used), which goes beyond restating the tool name. It does not explicitly distinguish itself from plausible neighbors like get_fusion_comp or get_clip, so it stops short of a 5.

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?

There is no explicit when-to-use statement or exclusion against alternatives; guidance is only implied by the enumerated target forms (clip grade, timeline, group pre/post). An agent can infer which contexts are queryable but not when another tool would be preferable.

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