Skip to main content
Glama
Sign In

AskEditor

by com.askeditor
OverviewDiscussionsAdmin

Remove timeline marker

remove_marker
Destructive

[write] Remove the ruler marker nearest to a time, within 120ms. With none that close it fails and changes nothing. Use to clear a flagged spot once it is dealt with. Not for clips (use delete_clip). Returns the refreshed timeline table, markers (ms, label), tracks and transitions. Related: add_marker, get_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": {
      "project_id": "<project_id>"
    },
    "name": "remove_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
msNoTimeline ms.
itemsNoMany markers at once, max 60, each with this tool's fields.
project_idYesThe AskEditor project this acts on (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the destructiveHint/write annotations, it discloses the 120ms proximity tolerance and the failure mode that matters most for a destructive tool: a miss fails and changes nothing. It also describes the return payload. It stops short of stating whether a batch with some near-matches partially applies, which would be the remaining behavioral risk.

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?

Front-loads the write marker and the core behavior, then proceeds through failure mode, usage, alternatives, and returns in a tight sequence of short sentences. A few shorthand constructions ('ms, label', tabular abbreviations) make it slightly terse, but no sentence is wasted.

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

Completeness5/5

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

For a 3-parameter destructive tool with no output schema, the description covers what it acts on, the matching rule, the failure behavior, the alternatives, and what comes back (timeline table, markers, tracks, transitions). An agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so parameter baseline is already satisfied, but the description adds real semantics to `ms` by explaining the nearest-within-120ms matching rule, which the schema's 'Timeline ms.' does not convey. The `items` batch parameter is only handled by the schema's maxItems=60, not by the description, keeping this below 5.

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

Purpose5/5

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

States a specific verb+resource (remove marker) and adds the precise rule that makes it distinctive: the marker nearest a time within 120ms. It also explicitly distinguishes itself from delete_clip, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('clear a flagged spot once it is dealt with') and an explicit when-not ('Not for clips (use delete_clip)'), plus related tools add_marker/get_timeline for adjacent needs. Nothing is left to inference.

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

All AskEditor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources