Skip to main content
Glama

set_timeline_mark_in_out

Set or clear a timeline's mark-in and mark-out frames in DaVinci Resolve, including video, audio, or all tracks, to define the range for edits.

Instructions

Set or clear a timeline's mark in/out (timeline frames).

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

Input Schema

NameRequiredDescriptionDefault
clearNo
mark_inNo
mark_outNo
timelineNo
mark_typeNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds only the clarifying note that values are in timeline frames; it does not explain whether clear=true overrides supplied marks, what happens when mark_in/mark_out are null, or whether out-of-range frames are clamped or rejected.

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 short sentence with the core action front-loaded and no filler. It is structurally clean, though its brevity leaves it under-specified rather than genuinely economical.

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 five undocumented parameters, no output schema, and no required fields, an agent cannot determine valid inputs or mode-selection rules from this definition. The annotation block covers safety but the parameter and behavior gap is large for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, so the description must compensate and it does not. It never explains the 'mark_type' enum (video/audio/all), what form the 'timeline' identifier takes, or how 'clear' interacts with 'mark_in'/'mark_out' — the only added meaning is the parenthetical 'timeline frames'.

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 names a specific verb pair ('set or clear') and a specific resource ('a timeline's mark in/out'), which separates it from the sibling set_clip_mark_in_out by scope (timeline vs clip). It is clear what the tool operates on, though it does not explicitly name the sibling as an alternative.

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 versus set_clip_mark_in_out, no prerequisites, and no statement of when clearing versus setting is appropriate. The word 'or' hints at two modes but the agent must infer the selection rule from the 'clear' flag in the schema.

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