Skip to main content
Glama

duplicate_timeline

Create a copy of a DaVinci Resolve timeline, with an optional name for the duplicate, to reuse edits or make variants without rebuilding sequences.

Instructions

Duplicate a timeline (optionally naming the copy).

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

Input Schema

NameRequiredDescriptionDefault
nameNo
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already establish this is a non-read-only, non-destructive, closed-world mutation. The description adds almost nothing beyond that: it does not say whether the duplicate copies markers/tracks/settings, whether the copy becomes the current timeline, or whether the original is affected. For a mutation with zero other coverage, this is a meaningful gap.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the missing behavioral and parameter detail noted above.

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 two undocumented optional parameters, no output schema, and no required fields, the definition leaves the agent unable to determine how the target timeline is identified or what a null target means. More text is needed here than for a simple read tool.

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 description must carry parameter meaning. It explains that `name` optionally names the copy, but says nothing about `timeline` — whether it is an ID, index, or name — nor what happens when it is omitted, despite both parameters being optional.

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 gives a specific verb and resource ("Duplicate a timeline") plus the scope of the optional naming behavior, which is more than a restatement of the name. It does not distinguish the tool from close siblings such as create_timeline or rename_timeline, so an agent must infer the difference.

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 statement of when to use duplication rather than creating a new timeline or renaming an existing one, and no prerequisites or exclusions. The only usage hint is the parenthetical that naming is optional.

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