Skip to main content
Glama

link_clip_media

Link or unlink proxy files, connect full-resolution media, replace clip media while preserving sub-clip extents, or monitor a growing file to keep DaVinci Resolve clips sourced correctly.

Instructions

Proxy and source media management for a clip: link/unlink a proxy file, link full-resolution media, replace the clip's media (optionally preserving sub-clip extents) or monitor a growing file.

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": {
      "clip": "<clip>",
      "action": "<action>"
    },
    "name": "link_clip_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
pathNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation profile is covered. The description adds real behavioral context beyond that: a replace mode optionally preserves sub-clip extents and one mode monitors a growing file. It does not say what replace does to existing media references, whether operations are reversible, or what a successful link returns.

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?

A single front-loaded sentence that leads with the resource category and then lists operations; there is essentially no filler. The dense enumeration is slightly hard to parse but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-mode mutation tool with no output schema and no parameter documentation, the description leaves too much open: path requirement per action, behavior on replace, and any result or error semantics are unstated. It is enough to know roughly what the tool is for, but not enough to call it correctly in all six modes.

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

Parameters2/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. It successfully explains the action enum's six values, but says nothing about the two other parameters: what 'clip' identifies, and when 'path' is required versus ignorable (unlink_proxy and monitor_growing_file plausibly need no path). An agent could still pass the wrong combination of clip/path/action.

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 (a clip's proxy/source media) and enumerates the concrete operations: link/unlink proxy, link full-resolution, replace, replace preserving sub-clip extents, monitor a growing file. This lets an agent map intent to the tool, though it never distinguishes the tool from nearby siblings such as link_items, clone_media or import_media.

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 implied through the action list, so an agent can infer that linking a proxy belongs here versus replacing media. There is no explicit when-to-use/when-not-to-use statement, no mention of prerequisites (media must be online, path must exist) and no routing to alternatives.

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