Skip to main content
Glama

get_item

Read-only

Retrieve details for a DaVinci Resolve timeline item, including properties, speed, fades, markers, versions, color, audio, cache, and stereo; optionally limit results to selected sections.

Instructions

Everything about a timeline item. sections (default all): basics, properties (transform, crop, composite, retime, stabilization...), speed, fades, markers, takes, versions, fusion, color, linked, audio, cache, output_blanking, stereo.

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": {
      "item": "<item>"
    },
    "name": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
sectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 genuine behavioral detail: the default returns all sections, and the enumerated section list tells the agent how broad the returned payload can be. It says nothing about error behavior, missing items, or payload size, so the added value is real but limited.

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

Conciseness4/5

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

Two short sentences, front-loaded, with the default behavior stated before the enumeration. The opening 'Everything about a timeline item' is slightly vague framing, and the trailing ellipsis in 'stabilization...' leaves the section list marginally open-ended, but otherwise nothing is wasted.

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 no output schema, the description carries the burden of indicating what comes back, and the section enumeration largely satisfies that. However, it does not explain the 'item' argument or what happens when a section is unavailable, so an agent getting the call right still has a gap. Adequate but with clear omissions for a read tool returning a broad payload.

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?

Schema coverage is 0%, so the description has to carry the load, and it does for the important parameter: it gives the full set of valid section names and states the default is all. The 'item' parameter is left unexplained (presumably an item identifier), which is the one remaining gap. Overall it adds substantial meaning beyond the bare schema.

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?

States a specific resource (a timeline item) and enumerates the data it returns (properties, speed, fades, markers, takes, versions, fusion, color, linked, audio, cache, output_blanking, stereo). That makes the scope concrete and separates it from purely structural siblings like get_timeline. It never explicitly names a contrasting sibling such as get_clip, so it stops short of full differentiation.

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 or when-not-to-use guidance; it never says to prefer this over get_clip or get_timeline for a given need. The only usage-adjacent signal is 'sections (default all)', which implies narrowing is possible. An agent must infer from the name and section list when this tool is the right call.

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