Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

get-highlight

Read-only

Retrieve a specific highlight by its unique ID to view saved content details. Use it when you need to fetch one highlight from Karakeep rather than searching all bookmarks.

Instructions

Retrieve a single highlight by id.

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": {
      "highlightId": "<highlightId>"
    },
    "name": "get-highlight"
  }
}

Input Schema

NameRequiredDescriptionDefault
highlightIdYesThe id of the highlight 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

B3.2/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a non-mutating read, so the description's contribution is minimal. It adds nothing about error behavior for missing ids, permission requirements, or what fields come back, which matters because no output schema is supplied.

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?

A single front-loaded sentence with no filler or redundant restatement of the title. Its brevity borders on under-specification rather than being padded, which keeps it efficient but leaves no room for routing guidance.

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 one-parameter read tool with a read-only annotation and full schema coverage, most of what an agent needs is already present. The remaining gap is behavioral: no statement of the return shape or of failure on a non-existent id, which the absent output schema leaves entirely to the description.

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?

With one parameter at 100% schema description coverage, the schema fully documents highlightId and its minLength constraint. The description adds no format hints (e.g., whether the id is a UUID or slug), 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 and resource ("Retrieve a single highlight") and constrains scope to one item fetched by id, which an agent can distinguish from list-highlights. It stops short of naming that sibling explicitly, so differentiation is inferred from the plural/singular naming rather than stated.

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?

Usage is implied by "single ... by id": fetch one record when the id is known. There is no explicit statement of when to prefer this over list-highlights or get-bookmark-highlights, and no mention of what happens for an unknown or deleted id.

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