Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

get-list-bookmarks

Read-only

Retrieve paginated bookmarks from a specific Karakeep list by its id, with smart lists evaluated using their saved query. Supports sorting, cursors, and optional full content.

Instructions

List bookmarks in a list by its stable id. Smart lists are evaluated using their saved query.

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": {
      "listId": "<listId>"
    },
    "name": "get-list-bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of bookmarks to return per page.
cursorNoCursor from a previous response to fetch the next page.
listIdYesThe id of the list whose bookmarks to retrieve.
sortOrderNoSort by creation date. Defaults to newest first.
includeContentNoWhether to include each bookmark's full content.

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.5/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description only needs to add context. It does add one genuinely non-obvious fact — smart lists are evaluated against their saved query, meaning results are dynamic and not a fixed membership set — but says nothing about pagination behavior or result volume beyond what the schema's cursor/limit already imply.

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?

Two short sentences, front-loaded with the core action and the stable-id keying, with the smart-list caveat placed after. Very little waste; only "by its stable id" borders on redundant wording.

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 read-only paged list tool with no output schema and full schema coverage, the description covers the essentials. However, it gives no sense of the returned collection's shape (bookmark summaries vs. content, which includeContent governs) or behavior when the list is empty or the id is unknown.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters (limit, cursor, listId, sortOrder, includeContent) are already documented, making the baseline 3. The description adds modest extra meaning by framing listId as a stable identifier and by signaling that contents may be optional (echoing includeContent), which nudges it above baseline.

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 bookmarks in a list") plus the keying mechanism ("by its stable id"), which is more precise than the name alone. It does not explicitly differentiate itself from close siblings such as get-tag-bookmarks or search-bookmarks, so it stops short of a 5.

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 only implied: an agent can infer this is the tool for enumerating a list's bookmarks. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. search-bookmarks for cross-list queries), leaving selection to inference.

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