Skip to main content
Glama

clips_select_info

Returns the clips currently selected in the DaVinci Resolve timeline UI, letting users identify clips by selecting them.

Instructions

Return the clips currently selected in the timeline UI (so the user can point at clips by selecting them).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clips_select_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It conveys the source of truth (live timeline UI selection state) and implies a safe read, but it does not state the return shape, what happens when nothing is selected, or whether the selection must be in a specific panel.

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?

One sentence with the core behavior front-loaded, and the parenthetical adds a genuine usage rationale rather than filler. It contains no redundant or repeated wording.

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?

This is a simple zero-parameter tool, so the description is close to adequate for its complexity. However, because no output schema exists, the description should say more about the shape of the returned clip list and the empty-selection case.

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?

The tool takes zero parameters, so this dimension reaches the baseline score of 4. No parameter meaning is needed or missing.

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?

It uses an explicit verb ("Return") and a precisely scoped resource ("the clips currently selected in the timeline UI"), which is clearly distinct from clip_info or clip_properties-style tools. It does not explicitly contrast itself with siblings, so it falls just 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?

The parenthetical "so the user can point at clips by selecting them" implies the workflow: the user makes a UI selection, then this tool reads it. However, it gives no explicit guidance on usage timing, when this is preferable to clip_info, or whether it works when no timeline is focused.

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