Skip to main content
Glama

bookmark_list

List bookmarks for the watched file in timeline order, or retrieve all files or a specific file's bookmarks. Each entry includes the ID needed to jump to it and the key it is filed under.

Instructions

Bookmarks for the file being watched, in timeline order. Pass all=true for every file, or file to ask about a specific one. Each entry carries the id that bookmark_goto takes, and the key it is filed under — the path for a file, the disc's own identity for a disc.

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoEvery file instead of just one.
keyNoExactly this identity, unresolved — from disc_list, get_status, or the `key` on a listed bookmark. Use it to reach bookmarks left under a drive letter before discs had an identity.
fileNoPath or URL. Defaults to what's playing. A drive path resolves to the disc currently in it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full disclosure burden, and it does add real behavior: results are returned in timeline order and each entry carries both the id accepted by bookmark_goto and the `key` it is filed under. That return-shape disclosure is valuable given there is no output schema. Remaining gaps are the default/empty-result behavior and any error conditions when nothing is playing.

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, front-loading the resource and ordering before the parameter guidance and the return-field note. No filler. The final clause about the disc's own identity is slightly dense but still earns its place by explaining the `key` value returned.

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 three-parameter, fully documented, read-only listing tool with no output schema, the description covers scope, ordering, parameter selection, and returned fields. The only meaningful omission is the no-argument default and empty-result behavior, which is a minor gap given the schema already states file defaults to what's playing.

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 description coverage is 100% and the schema already explains all, key, and file in detail, including that key is unresolved and that a drive path resolves to the disc currently in it. The description largely restates that selection logic rather than adding syntax, formats, or precedence rules between `all`, `key`, and `file`. Baseline 3 applies when the schema does the heavy lifting.

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?

States the resource (bookmarks), the scope (the file being watched), and the ordering (timeline order) in the opening sentence, which is enough to distinguish it from the write-oriented siblings bookmark_add/remove/clear/rename. It even names bookmark_goto as the consumer of the returned id. It stops short of an explicit 'list vs. write' contrast, so it is clear but not maximally differentiating.

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?

'Pass all=true for every file, or file to ask about a specific one' gives concrete guidance on choosing between parameters, and pointing at bookmark_goto for the returned id shows the intended hand-off. However, there is no guidance on when to reach for this tool versus siblings, nor any statement of what happens with no arguments or when no file is playing.

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