Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

get-bookmark

Retrieve a bookmark by ID from Karakeep to access its saved details.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
bookmarkIdYesThe bookmarkId to get.

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. Changed1 schema field changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about what is returned, whether content/highlights are included, or how a missing or invalid id is handled (error vs. empty). The only implicit behavior is exact lookup by id rather than search, which is thin for a tool with zero annotation coverage.

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 short sentence that is front-loaded and free of filler. Its brevity is efficient, though it verges on under-specification rather than being genuinely concise.

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 fully documented schema and no output schema, the description covers the minimum needed to attempt a call. It falls short on return-value expectations and the distinction from the many sibling bookmark getters, which an agent would need to choose correctly.

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% and the single parameter (bookmarkId) is documented in the schema, so the baseline is 3. The description's "by id" phrasing adds no format, sourcing, or validity detail beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ("Get a bookmark"), so the basic operation is identifiable. However, "by id" is the only qualifier, and it does not distinguish this tool from siblings such as get-bookmark-content, get-bookmark-highlights, or get-bookmark-lists, leaving ambiguous whether the returned bookmark includes content, highlights, or list membership.

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 when-to-use guidance at all: no statement about preferring search-bookmarks when the id is unknown, and no mention of the sibling tools that return bookmark sub-resources. The agent must infer usage purely from the name.

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