Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

delete-bookmark

Permanently deletes a bookmark by ID, removing the bookmark along with its highlights and assets.

Instructions

Delete a bookmark by id. This is destructive — the bookmark, its highlights, and its assets are removed.

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": {
      "bookmarkId": "<bookmarkId>"
    },
    "name": "delete-bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmarkIdYesThe id of the bookmark to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.35.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key behavioral trait: this is destructive and removes not just the bookmark but its highlights and assets. It omits irreversibility wording, permission/auth requirements, and what happens if the id does not exist, so it stops short of full coverage.

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 with no waste: the operation and selector come first, the destructive cascade warning second. Every clause carries information an agent needs.

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 simple one-parameter mutation with no output schema and no annotations, the description covers the essentials of what is destroyed and by what key. It falls slightly short by leaving out error behavior for an invalid id and any note on obtaining valid bookmark ids.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents bookmarkId fully. The description only echoes 'by id' with no added format, source, or validation meaning, which is the expected baseline for a fully documented one-parameter tool.

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 and resource ('Delete a bookmark') plus an exact selector ('by id'), and adds that the deletion cascades to highlights and assets. That cascade detail distinguishes it in practice from delete-highlight, which removes only a highlight.

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 destructive note implies you should think twice before calling, and the cascade hints that delete-highlight may be preferable when only a highlight should go. But there is no explicit when-to-use guidance, no statement of prerequisites, and no named alternative tool.

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