Skip to main content
Glama

bookmark_add

Save a named position in a file to jump back to it later; defaults to the current playback spot and persists across sessions.

Instructions

Save a named position in a file, so it can be jumped back to later. Defaults to where playback is right now in the file the user is watching. Bookmarks persist across sessions and are recorded even in incognito mode, since they are asked for explicitly.

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

Input Schema

NameRequiredDescriptionDefault
fileNoPath or URL. Defaults to what's playing.
nameNoLabel for the spot. Omit and it shows as its timestamp.
positionNoSeconds into the file. Defaults to the current position; required when bookmarking a file that isn't playing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole burden. It usefully discloses persistence across sessions and that bookmarks are still recorded in incognito mode, which is genuinely beyond-schema context. But it says nothing about what the call returns (an identifier? the bookmark object?), nothing about duplicate or overwritten names, and nothing about failure modes such as an unplayable or nonexistent file, leaving the mutation's consequences under-specified.

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?

Three short sentences, front-loaded with the core action and effect, and each sentence contributes (persistence and incognito behavior are non-obvious). Slight redundancy with the schema's default descriptions, but nothing is padding.

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 zero-required-parameter tool with full schema coverage and no output schema, the description covers purpose, defaults, and persistence adequately. The one real gap is return-value behavior, which is unstated and unbacked by an output schema, so an agent cannot tell what it gets back on success.

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?

Schema coverage is 100%, and the description largely restates what the schema already documents: default file from playback, default name from timestamp, and position required when the file is not playing. It adds no new syntax, format, or constraint guidance beyond the structured fields, so the baseline 3 applies.

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?

"Save a named position in a file, so it can be jumped back to later" gives a specific verb (save) and resource (named position in a file) plus the payoff. It does not explicitly contrast itself with bookmark_goto / bookmark_list / bookmark_rename, so an agent must infer the split from sibling names alone.

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?

Usage is implied rather than stated: the default-to-current-playback behavior tells the agent this is the right call while media is playing. There is no explicit when-to-use versus bookmark_goto, and no statement of when not to call it or how it relates to bookmark_list.

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