Skip to main content
Glama

get_selected_items

Read-only

Retrieves the timeline items currently selected in the DaVinci Resolve UI, optionally from a specified timeline, so agents can act on the user's active selection.

Instructions

Timeline items currently selected in the UI.

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": "get_selected_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the result reflects live UI selection state rather than a stored query, which implies a volatile snapshot. It does not say what is returned when nothing is selected or whether the result is ordered.

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?

It is short and front-loaded, but it is a sentence fragment rather than a complete statement, so brevity comes at the cost of a clear predicate. Nothing is wasted, yet nothing is fully said.

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 simple read tool with no output schema, the description should at least say what a returned item looks like and how the timeline parameter scopes the result. Neither is present, leaving the agent to guess at both the return shape and the parameter's effect.

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% and the single optional 'timeline' parameter is never mentioned in the description. The agent cannot tell whether omitting it means 'active timeline' or 'all timelines', nor what the string vs integer union accepts. With one undocumented parameter, the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase names a specific resource (timeline items) and a specific scope (currently selected in the UI), which distinguishes it from get_selected_clips and list_track_items. But it is a bare noun phrase with no verb, so the agent must infer that it retrieves rather than, say, reports or highlights them.

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 when-to-use guidance, no mention of the sibling get_selected_clips or how items differ from clips, and no statement about what happens when the selection is empty. The agent is left to infer the calling context entirely from the name.

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