Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

create-bookmark

Create link or text bookmarks in Karakeep by supplying a URL or text content, with an optional title.

Instructions

Create a link bookmark or a text bookmark

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": {
      "type": "<type>",
      "content": "<content>"
    },
    "name": "create-bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe type of bookmark to create.
titleNoThe title of the bookmark
contentYesIf type is text, the text to be bookmarked. If the type is link, then it's the URL to be bookmarked.

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. Addedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about what happens on creation, whether duplicates are rejected, what permissions are needed, or what is returned. Only the mutation itself is implied by the verb 'Create'.

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 with no wasted words, front-loaded with the verb. Its brevity is efficient, though it borders on under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description omits the outcome (what a created bookmark looks like, its ID, default list membership) and any error or permission behavior. An agent can call it, but cannot anticipate results.

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%, so the type enum and the conditional meaning of 'content' (text vs URL) are already fully documented in the schema. The description restates the link/text distinction without adding format, length, or validation details beyond it.

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 ('Create a ... bookmark') and distinguishes the two variants it supports (link vs text). It doesn't explicitly differentiate itself from siblings such as create-highlight or create-list, but the resource name is distinct enough for selection.

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, no prerequisites, and no mention of alternatives or follow-up tools (e.g., attach-tag-to-bookmark, add-bookmark-to-list). An agent must infer usage purely from the tool name and schema.

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