Skip to main content
Glama

add_markers

Add sequence markers at edited-timeline seconds to label chapter points, highlights, or notes, helping users find key moments.

Instructions

Add sequence markers (edited-timeline seconds), e.g. chapter points, highlights, or notes for the user.

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

Input Schema

NameRequiredDescriptionDefault
markersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add genuinely useful behavioral context by specifying the time base is edited-timeline seconds rather than source media time, which prevents a common misuse. However, it says nothing about whether markers are appended versus replacing existing ones, permission requirements, duplicate-time handling, or what the call returns.

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 tight sentence with the core purpose front-loaded and no filler. The parenthetical is doing real work rather than padding, though the examples slightly dilute the focus.

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

Completeness4/5

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

For a single-parameter tool with no output schema and no annotations, the description covers purpose, the time reference frame, and typical use cases. The notable remaining gaps are the semantics of the marker object's other fields and append-versus-replace behavior.

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?

There is one parameter, but it is a nested array of marker objects (time, name, color, comment, duration) with 0% schema description coverage. The description usefully defines the unit and frame of reference for `time`, the most error-prone field, but leaves name, color, comment, and duration entirely undocumented in both schema and description.

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?

Specific verb plus resource: "Add sequence markers" with a clarifying parenthetical that markers are positioned in edited-timeline seconds, plus concrete examples (chapter points, highlights, notes). It does not distinguish itself from siblings like add_zooms or make_captions, but the operation itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The examples ("chapter points, highlights, or notes for the user") imply intended use cases, giving implied guidance rather than explicit ones. There is no statement of when not to use this tool, no prerequisites, and no reference to alternatives for time-based annotations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.