Retrieves all timelines in the active DaVinci Resolve project, providing each timeline's name, index, duration, and track counts.
List all timelines in the current project.
Returns JSON array with each timeline's name, index, duration, and track counts.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v2.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden. It explicitly states the read-only list behavior and what the JSON array contains. It does not mention failure modes such as requiring an open project, but this is minor for a zero-parameter list operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is composed of two focused sentences: the first states the action and scope, the second specifies the output shape. There is no fluff or unnecessary detail, and the core purpose is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter enumeration tool with an output schema available, this description is complete. It identifies the resource, limits it to the current project, and summarizes the returned data. Nothing required to invoke the tool correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there are no parameter semantics for the description to clarify. The schema coverage is 100% and there is no parameter documentation gap, so the baseline score of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and object: 'List all timelines in the current project.' It also describes the output fields, making it easy to distinguish from sibling tools such as resolve_get_current_timeline, resolve_set_current_timeline, or resolve_create_timeline.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly establishes when to use it: when the agent needs all timelines in the currently loaded project. It scopes usage to the current project and, by naming 'all timelines', implicitly differentiates from single-timeline operations. It does not explicitly name alternatives, but the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.