Skip to main content
Glama

media_link

Relink, replace, unlink, or proxy DaVinci Resolve media items by folder or file path, including full-resolution links and growing-file monitoring for broken or moved assets.

Instructions

Relink / replace / proxy operations. action: 'relink' (items → media in folder path), 'unlink', 'replace' (single item → file path), 'replace_keep_subclip', 'proxy_link' (proxy file path), 'proxy_unlink', 'full_res_link' (full-res file path), 'monitor_growing'.

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": {
      "items": "<items>",
      "action": "<action>"
    },
    "name": "media_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
itemsYes
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden for a clearly mutating tool that relinks, replaces, and unlinks media. It never states permission requirements, whether relinking is reversible, what happens to clips whose media is unlinked, or what is returned. The directional notation (items → media in folder path) is the only behavioral hint.

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 description is compact and front-loads the operation family before the action breakdown, with no filler. The parenthetical glosses are efficiently terse, though 'monitor_growing' is left entirely unexplained and the punctuation is dense.

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 annotations and no output schema, covering every action is a solid start, but behavioral and safety context is absent and one action is opaque. An agent can choose an action yet cannot predict side effects or results.

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% and `action` has no enum in the schema, so the description's enumeration of action values is essential and effectively supplies the missing enum. It also disambiguates `path` per action (folder vs single file vs proxy file vs full-res file). It only weakly characterizes `items` (format of the item references is unstated).

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 specific verbs (relink, unlink, replace, proxy_link, full_res_link) and the resource they act on, plus enumerates the action values. It doesn't differentiate from the sibling clips_link or clarify what 'monitor_growing' does, 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?

By mapping each action string to an intent and its meaning for `path` (folder for relink, file for replace, proxy file for proxy_link), the description implicitly tells an agent which action to pick. However, it gives no when-not guidance, no prerequisites, and never names an alternative tool for related link operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.