Skip to main content
Glama

get_markers

Read-only

Retrieve markers for a timeline, timeline item, or media pool clip keyed by frame, or get the single marker matching custom_data.

Instructions

Markers of a timeline, timeline item or media pool clip, keyed by frame (or the one marker with custom_data). Timeline markers are relative to the timeline start.

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

Input Schema

NameRequiredDescriptionDefault
targetNotimeline
custom_dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: results are keyed by frame, timeline markers are expressed relative to the timeline start (a non-obvious coordinate convention), and custom_data narrows to a single marker rather than a list. It stops short of saying what an empty or unmatched result looks like.

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?

Two tight sentences with no filler, and the return-keying and coordinate convention are front-loaded. The first sentence is a fragment lacking a verb, which costs a little clarity but not length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema and no parameter descriptions, the description covers return shape and coordinate semantics but omits the literal target vocabulary and default. That gap is exactly what an agent needs to construct a valid call, so the definition is adequate but not self-sufficient.

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

Parameters3/5

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

With 0% schema description coverage, the description is the only source of parameter meaning, and it does clarify that custom_data selects one specific marker. However, it never enumerates the accepted target values (timeline, timeline item, clip identifiers) or their string form, nor mentions the 'timeline' default, so an agent must guess the literal argument.

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?

Names the resource precisely (markers of a timeline, timeline item, or media pool clip) and the keying scheme (by frame), which is enough to distinguish it from the mutating siblings add_markers and delete_markers. It is a noun phrase without an explicit verb such as 'retrieve', so the read intent comes partly from the name and annotations rather than the text.

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 call this versus alternatives, no prerequisites, and no guidance about which target to choose. The only implicit use hint is the parenthetical that passing custom_data returns 'the one marker' matching it, which is a behavior note rather than a when-to-use rule.

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