Skip to main content
Glama

rename_timeline

Renames a DaVinci Resolve timeline by applying a new name, optionally targeting a specific timeline, so project timelines stay accurately labeled.

Instructions

Rename a timeline.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no mention of whether the rename persists, whether it fails on duplicate names, or whether it affects the currently open timeline — the key behavioral question given the optional 'timeline' parameter.

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?

The single sentence is front-loaded and wastes no words, but its brevity comes from under-specification rather than efficiency. There is no structure to speak of — no scope, parameters, or caveats to organize.

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 two-parameter mutation with no output schema and no annotation-documented return behavior, the description is far too thin. It should at minimum explain how the target timeline is selected and what the result is, neither of which is present.

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 carries the full burden, and it does not. The critical ambiguity — whether 'timeline' accepts a name, an index, or null meaning the current timeline — is entirely unexplained, and 'name' is never described as the new name versus a lookup key.

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

Purpose2/5

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

The description restates the tool name verbatim: 'Rename a timeline' adds no verb nuance, scope, or resource detail beyond what 'rename_timeline' already conveys. It does not distinguish this from sibling renames such as rename_project, nor clarify what a 'timeline' is in this context.

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 guidance on when to use this tool, no prerequisites, and no mention of alternatives (e.g., duplicate_timeline or set_timeline_settings). The agent must infer everything from the tool name alone.

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