Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

get-bookmark-content

Retrieve a bookmark's saved content as Markdown using its bookmark ID, making the full text available for reading or processing.

Instructions

Get the content of the bookmark in markdown

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-content"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmarkIdYesThe bookmarkId to get content for.

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

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose the output format (markdown), which is a genuine behavioral detail beyond the schema, and the read-only nature is evident from 'Get'. However, it says nothing about what happens when content is absent, whether it can fail, or how large content is handled.

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 no wasted words, and the format detail is placed where it is immediately useful. Slightly terse given the absence of any usage or behavioral context.

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 simple single-parameter read tool with full schema coverage and no output schema, the description covers the core action and return format. It is adequate but leaves gaps around edge cases and sibling disambiguation that an agent could need.

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 bookmarkId parameter is documented in the schema itself. The description adds no meaning beyond that, so the baseline of 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 ('Get the content of the bookmark') and adds the return format ('in markdown'), which distinguishes it from get-bookmark metadata retrieval implicitly. It does not explicitly name or contrast with the sibling get-bookmark, 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 Guidelines2/5

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

There is no guidance on when to use this versus get-bookmark, get-bookmark-highlights, or search-bookmarks, and no stated preconditions or exclusions. The agent must infer that this fetches full body content rather than metadata.

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