Skip to main content
Glama

move_clips

Move clips to a target bin in DaVinci Resolve to reorganize media and keep project assets grouped.

Instructions

Move clips to another bin.

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>",
      "target_bin": "<target_bin>"
    },
    "name": "move_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
target_binYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation. The description adds nothing beyond that: it does not say whether the clips are removed from the source bin, whether the target bin must already exist, whether the operation is atomic across multiple clips, or what happens on partial failure. With annotations carrying only the safety profile, the description leaves real behavioral questions unanswered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but here brevity comes at the cost of the missing information above. It is efficiently written but under-specified relative to a two-required-parameter mutation.

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 mutation tool with zero schema coverage, no output schema, and no param documentation anywhere, the definition is too thin. An agent calling it correctly needs to know identifier formats, target-bin validity requirements, and error/partial-success behavior, none of which are present.

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 must compensate, and it does not. It never clarifies whether 'clips' are unique IDs, names, or indices, nor whether 'target_bin' is a bin name or ID, nor what a full bin or nonexistent bin does.

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 verb and resource ('Move clips') plus the destination concept ('to another bin'), so an agent knows exactly what operation this is. It does not differentiate itself from the sibling move_bins or explain how it relates to list_clips/get_selected_clips, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus move_bins, or how to obtain the clip identifiers to pass in. The sentence states capability only, leaving all routing and prerequisite decisions 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