Skip to main content
Glama

item_ai

Apply AI operations to a DaVinci Resolve timeline item: track or regenerate Magic Mask, stabilize footage, or Smart Reframe clips.

Instructions

AI tools on a timeline item: Magic Mask (track forward F / backward B / both BI), regenerate Magic Mask, Stabilize, Smart Reframe. Requires Resolve Studio.

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": {
      "item": "<item>",
      "action": "<action>"
    },
    "name": "item_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
actionYes
directionNoBI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, closed-world operation, so the safety profile is partly covered. The description adds the Studio-license prerequisite, which is genuinely useful. It does not disclose whether masks/stabilization are applied destructively to the clip, how long the operation takes, or what happens to existing masks on regenerate — gaps that matter for a mutation tool.

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 dense lines: capability list first, constraint last. No filler sentences, and the terse parenthetical is doing real work by decoding the direction codes.

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 3-parameter mutation tool with no output schema, the definition covers what it does and the direction codes but omits behavioral detail an agent would want — whether operations are async/long-running, whether prior masks are overwritten, and what the result payload looks like on failure.

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 must compensate, and it largely does: the parenthetical 'track forward F / backward B / both BI' defines the direction enum values that the schema leaves cryptic. The action enum is effectively mirrored by the enumerated feature list, though the 'item' parameter itself is never characterized.

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 scope ('on a timeline item') and enumerates the four concrete operations (Magic Mask, regenerate, Stabilize, Smart Reframe), so an agent knows exactly what capability this exposes. It stops short of explicitly contrasting itself with timeline-level AI tooling, so the item-vs-timeline distinction is inferable from the name rather than stated.

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?

It gives a hard prerequisite ('Requires Resolve Studio') and implies the scope is per-item, but offers no when-to-use/when-not guidance and no named alternative for timeline-wide AI operations. Adequate context, no routing.

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