Skip to main content
Glama

select_clip

Select a clip in the DaVinci Resolve media pool to target it for subsequent media operations.

Instructions

Select a clip in the media pool.

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

Input Schema

NameRequiredDescriptionDefault
clipYes

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 only declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description does not explain what 'select' actually changes, whether it replaces an existing selection, whether it requires the media pool to be open, or what happens if the clip is missing — a real gap given readOnlyHint=false implies state mutation.

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 efficient and front-loaded with no wasted words, but its brevity comes at the cost of under-specification rather than genuine conciseness.

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?

With no output schema and a bare annotation set, the description carries the burden of explaining return behavior, error conditions, and the meaning of the clip argument. It supplies none of these, so an agent cannot reliably invoke the tool beyond guessing the argument format.

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 single required 'clip' parameter has no documented format in either the schema or the description. It is unclear whether the value is a name, path, unique ID, or index, which is exactly what the description should compensate for at this coverage level.

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 states a specific verb and resource: 'Select a clip in the media pool.' An agent can tell this is a selection action on a clip object, though nothing distinguishes it from siblings like get_clip or update_clip.

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 select versus fetch (get_clip) or modify (update_clip) a clip, no preconditions, and no stated alternatives. The agent must infer that selection is a UI/state operation distinct from retrieval.

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