Skip to main content
Glama

bookmark_clear

Deletes every bookmark for the file being watched or for a named file, with an opt-in all=true flag required to clear bookmarks across all files.

Instructions

Delete every bookmark for the file being watched, or for the file named. Pass all=true to delete them for every file — that scope is never reached by default.

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

Input Schema

NameRequiredDescriptionDefault
allNoEvery bookmark, for every file.
keyNoExactly this identity, unresolved — from disc_list, get_status, or the `key` on a listed bookmark. This is how bookmarks orphaned under a drive letter are deleted.
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.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the blast-radius guard (bulk deletion only via explicit all=true), but says nothing about irreversibility, confirmation behavior, or what happens when no bookmarks match — meaningful gaps for a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, action and default scope front-loaded, with the escalation condition placed last where it reads naturally. No filler or repetition of the schema.

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 zero-annotation destructive bulk tool with no output schema, the scope semantics are covered well, but the description omits outcome behavior — return value, empty-result handling, and reversibility. Adequate but not complete for a delete-everything operation.

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%, so the schema already documents all, key, and file in detail, including the orphaned-drive-letter case for key. The description reinforces the default-scope behavior of file and the all flag but adds no new meaning for key, so 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?

States a specific verb and resource ('Delete every bookmark') plus the two scopes it operates on (current/named file vs. every file via all=true). The scope distinction makes it distinguishable in spirit from a single-item remover like bookmark_remove, though no sibling is named explicitly.

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 description makes the default scope and the all=true opt-in clear ('that scope is never reached by default'), which is real usage guidance. It never says when to reach for this instead of bookmark_remove or bookmark_list, so the when-to-use guidance against siblings is only implied.

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