Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

list-highlights

Read-only

List highlights across all bookmarks in newest-first order and paginate results with limit and cursor parameters.

Instructions

List highlights across all bookmarks, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of highlights to return per page.
cursorNoCursor from a previous response to fetch the next page.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavior beyond that — a global scope and a defined sort order ('newest first') — but says nothing about pagination behavior or result volume, even though the cursor parameter shows paging exists.

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?

One short sentence, front-loaded with the action and immediately followed by the scope and ordering constraint. Nothing is wasted and nothing is buried.

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?

This is a simple two-optional-parameter read tool with a fully documented schema and readOnlyHint, so little needs explaining. A brief note on default page size or whether ordering can be changed would close the remaining gap.

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%: both limit and cursor are fully documented in the schema, including the cursor's round-trip semantics. The description adds no parameter-level detail, 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?

States a specific verb and resource ('List highlights') plus the scope 'across all bookmarks', which implicitly separates it from the per-bookmark sibling get-bookmark-highlights. It does not name that sibling explicitly, so the differentiation is inferential 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?

The phrase 'across all bookmarks' implies this is the global/unfiltered listing option, which lets an agent infer when to prefer it over a bookmark-scoped call. However, there is no explicit when-to-use or when-not guidance and no named alternative.

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