Skip to main content
Glama

set_marker_custom_data

Sets the custom data string for a timeline marker at a specified frame, enabling agents to store or update marker metadata in DaVinci Resolve.

Instructions

Set the custom data string of the marker at frame.

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": {
      "frame": "<frame>",
      "custom_data": "<custom_data>"
    },
    "name": "set_marker_custom_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameYes
targetNotimeline
custom_dataYes

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 declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent already knows this is a non-destructive local mutation. The description adds nothing beyond that: it does not say whether existing custom data is replaced wholesale, what happens if no marker exists at `frame`, or whether the call errors or silently no-ops. For a mutation tool, that behavioral gap matters.

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?

One short sentence with the identifying constraint ('at `frame`') included and no filler — the size is appropriate. It is under-specified rather than bloated, so conciseness itself is a strength.

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 three parameters at 0% schema coverage, a mutation annotation profile, and no output schema, the description should cover the `target` parameter, overwrite semantics, and missing-marker behavior. It covers only the basic operation, leaving an agent unable to call this correctly in edge cases.

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 the load, but it only glosses `frame` and `custom_data` implicitly and says nothing about `target`, which has a default of 'timeline' and no documented alternative values or effect. The most confusing parameter is left entirely unexplained.

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 ('Set the custom data string of the marker') plus the locating dimension ('at `frame`'), which cleanly separates it from sibling tools like add_markers or set_timeline_mark_in_out. It stops short of 5 because the scope of 'marker' is ambiguous given an undocumented `target` parameter that defaults to 'timeline'.

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 versus alternatives such as add_markers or set_clip_mark_in_out, and no prerequisites are stated. The description also never explains what switching `target` away from the default implies, so an agent cannot reason about which variant of the operation it is requesting.

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