Skip to main content
Glama

relink_clips

Relink selected clips to media files in a specified folder, or unlink them, to repair missing media connections in DaVinci Resolve.

Instructions

Relink clips to media found under folder_path, or unlink them (unlink=true).

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": {
      "clips": "<clips>"
    },
    "name": "relink_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
unlinkNo
folder_pathNo

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=false, destructiveHint=false, and openWorldHint=false, so the mutation profile is covered. The description adds the useful scoping fact that media is resolved under a caller-supplied folder. It omits what happens when matching media is not found, whether the operation is reversible, and whether it acts on selection or only the passed clips.

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?

A single sentence, front-loaded with the primary action and appending the alternate mode with its trigger flag. No filler, no restating of the tool name.

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?

With three parameters, no output schema, and a non-destructive write annotation, the description covers the core action adequately. It remains thin on failure behavior and on the format of the required clips argument, which is the main thing an agent could get wrong when invoking it.

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

Parameters3/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 burden. It does explain the semantics of folder_path (the media location searched) and unlink (true reverses the operation), but the required clips array is left unexplained — no indication whether the strings are IDs, names, or paths, or whether order matters.

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 pairs a specific verb pair (relink/unlink) with the resource (clips) and names the scoping input (folder_path). An agent immediately knows this rewires or removes clip-to-media associations. It stops short of distinguishing itself from neighbors like move_clips or delete_clips, so it is clear but not sibling-differentiated.

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 states the two operating modes and the flag that selects the second (unlink=true), which is implied when-to-use guidance. It never says when NOT to use it, nor does it point to an alternative such as move_clips for relocating rather than relinking, leaving the choice to inference.

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