audiobookshelf-mcp

Overview Schema Source Related Servers Discussions Admin

Delete bookmark

delete_bookmark

DestructiveIdempotent

Delete a bookmark at a specified time position after user confirmation. Requires the bookmark's library item ID, time position, and a confirmation token.

Instructions

Deletes the bookmark at a given position. Asks a person first; where the client cannot show a dialog, call once to receive a token and again with it.

Input Schema

TableJSON Schema

Name	Required	Description
`time`	Yes	Position in seconds identifying the bookmark
`confirm_token`	No	Token from the first call of this tool
`library_item_id`	Yes	Library item id, as returned by list_library_items or search_library

Output Schema

TableJSON Schema

Name	Required	Description	Default
`truncated`	No	Present only when the answer was shortened to fit the budget.
`deleted_bookmark`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.4.0Sep 8, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / confirm_token

Added value: +{
+  "description": "Token from the first call of this tool",
+  "maxLength": 128,
+  "type": "string"
+}

addedInput schema / properties / library_item_id / maxLength
```
Added value: +128
```
addedInput schema / properties / time / maximum
```
Added value: +1000000000
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "deleted_bookmark": {
+      "additionalProperties": false,
+      "properties": {
+        "item_id": {
+          "type": "string"
+        },
+        "time": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "item_id",
+        "time"
+      ],
+      "type": "object"
+    },
+    "truncated": {
+      "additionalProperties": false,
+      "description": "Present only when the answer was shortened to fit the budget.",
+      "properties": {
+        "dropped_entries": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "follow_up": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason",
+        "dropped_entries",
+        "follow_up"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "deleted_bookmark"
+  ],
+  "type": "object"
+}

First observedv0.1.1Aug 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description transparently notes both the destructive nature ('Deletes') and the need for human confirmation or a confirm token. The annotation already marks destructiveHint and idempotentHint, and the description adds useful detail about the token-based flow, though it does not explicitly discuss idempotency semantics.

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?

The description is two succinct sentences with no redundant wording. It efficiently communicates the core action and the confirmation requirement without unnecessary detail.

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?

The description provides sufficient context for a destructive, confirmation-required delete operation and explains the token flow for non-dialog clients. It does not describe the output schema, but that is not necessary given the simple operation and available annotations.

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?

The schema already covers all parameters with descriptions, including the role of time, confirm_token, and library_item_id. The description adds little parameter-specific meaning beyond referring to 'position' and 'token', so it meets the baseline for high schema coverage.

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?

The description clearly states the action ('Deletes the bookmark') and the target ('at a given position'), distinguishing it from create/update bookmark tools. It also references the library item context via schema parameters, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides concrete usage guidance for the two-call confirmation flow, including the fallback for clients that cannot show a dialog. It does not explicitly compare with alternatives, but the deletion purpose and confirmation requirement are adequately conveyed.

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