Skip to main content
Glama

call_api

Destructive

Invoke any DaVinci Resolve API method by specifying a target, method name, and JSON arguments—enabling agents to control projects, media, timelines, and other Resolve features.

Instructions

Call ANY Resolve API method: target is a reference ("project", "media_pool", "timeline", "item:", "clip:", "graph:item:", "handle:", ...), method the API method name (see list_api_methods) and args its positional arguments as JSON. Inside args, objects are {"$ref": "..."} and constants {"$const": "NAME"}. Returned objects come back as references.

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>",
      "method": "<method>"
    },
    "name": "call_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
methodYes
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 destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the reference-encoding protocol ({"$ref": ...}, {"$const": ...}) and that returned objects come back as references rather than materialized values. It does not explain error behavior, whether side effects depend on the chosen method, or how references are obtained in the first place.

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?

The core action is front-loaded in the first clause, and the remaining text is dense, purposeful specification of the target/method/args contract with no filler. The parenthetical list of reference forms is long but earns its space given 0% schema coverage.

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 destructive, open-ended dispatcher with no output schema and undocumented parameters, the invocation mechanics are covered well, but an agent still lacks guidance on obtaining references, handling failures, and choosing this tool over the numerous dedicated siblings. Adequate, not complete.

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 coverage is 0%, so the description carries the full burden, and it largely succeeds: `target` is enumerated with concrete reference forms ('project', 'media_pool', 'timeline', 'item:<uid>', 'graph:item:<uid>', 'handle:<n>'), `method` is tied to list_api_methods, and `args` is defined as positional JSON with $ref/$const conventions. It stops short of saying how uids are sourced or whether argument order must exactly match the API signature.

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?

States a specific verb and resource ('Call ANY Resolve API method') and immediately defines the three-part invocation shape (target, method, args), so an agent knows exactly what the tool does. It does not differentiate itself from the many dedicated sibling tools (add_markers, create_bin, delete_items) that likely wrap the same underlying methods, so it falls 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?

Points the agent to list_api_methods for discovering method names, which is genuine routing guidance for the `method` parameter. However, it gives no when-to-use/when-not guidance relative to dedicated siblings, no statement that this is the escape hatch for methods without a dedicated tool, and no warning about preferring safer wrappers.

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