Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

add-bookmark-to-list

Add a bookmark to a specified list by providing the list ID and bookmark ID, so you can organize saved items into collections.

Instructions

Add a bookmark to a list.

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>",
      "bookmarkId": "<bookmarkId>"
    },
    "name": "add-bookmark-to-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe listId to add the bookmark to.
bookmarkIdYesThe bookmarkId to add.

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.3/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 burden of behavioral disclosure, and it says nothing about idempotency (what happens if the bookmark is already in the list), permission requirements, side effects, or ordering within the list. 'Add' does signal a mutation, which is the only behavioral hint offered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, so it wastes nothing. However, its brevity is under-specification rather than economy, given that a mutation tool with two required identifiers needs more than one clause.

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?

With no annotations and no output schema, the description is the only place behavioral context could live, and it supplies none. An agent can form the call from the schema alone but cannot know duplicate handling, failure modes, or what the response confirms.

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%, with both listId and bookmarkId documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, but nothing is left undocumented at the parameter level.

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

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description "Add a bookmark to a list" is essentially a restatement of the tool name add-bookmark-to-list, adding no scope, constraints, or distinguishing detail. It does convey the verb and resource, but nothing an agent could not already infer from the name itself.

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 or when-not-to-use guidance, and no mention of the sibling remove-bookmark-from-list or of any prerequisites such as the list or bookmark needing to exist. The agent must infer the call context entirely from the name.

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