Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

get-bookmark-highlights

Read-only

Retrieve all highlights for a bookmark by ID, enabling quick review of saved passages in one place.

Instructions

List every highlight on a bookmark.

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": "get-bookmark-highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmarkIdYesThe id of the bookmark whose highlights to retrieve.

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. Addedv0.33.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the description contributes nothing about safety. It also omits ordering, pagination, empty-result behavior, and whether highlights are returned inline or as references — all things an agent would want for a listing call that has no output schema to explain the return shape.

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?

One short sentence with the resource and scope front-loaded, and no filler. It is efficient but slightly under-specified rather than padded, so it stops short of a 5.

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?

This is a simple single-parameter read tool whose annotations cover the safety profile, so the description need not do much. However, with no output schema, the description could have said what a highlight record roughly contains or whether results are paginated, and it does not.

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 single parameter 'bookmarkId' is already documented in the schema as the bookmark whose highlights to retrieve. The description adds no format hints, id-source guidance, or validation notes beyond that, 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?

The description names a specific verb ('List') and resource ('every highlight on a bookmark'), so the operation and its scope are unambiguous. It stops short of differentiating itself from the sibling 'list-highlights', which an agent could easily confuse with this scoped variant.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no mention of the obvious alternative ('list-highlights') or the prerequisite that a valid bookmark id is needed. The only guidance is inferable from the broad scope phrase, leaving the agent to guess at routing.

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