Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

update-bookmark

Modify selected fields on an existing bookmark while leaving omitted fields unchanged; returns the updated bookmark.

Instructions

Update fields on an existing bookmark. Only the fields you pass are modified; omitted fields stay unchanged. Returns the updated 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": {
      "bookmarkId": "<bookmarkId>"
    },
    "name": "update-bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoNew URL for a link bookmark.
noteNoA free-form note on the bookmark.
titleNoThe bookmark's user-set title. Pass null to clear it.
authorNoLink author. Pass null to clear it.
summaryNoThe bookmark's summary. Pass null to clear it.
archivedNoWhether the bookmark is archived.
createdAtNoOverride the bookmark's createdAt timestamp (ISO 8601).
publisherNoLink publisher. Pass null to clear it.
bookmarkIdYesThe bookmarkId to update.
favouritedNoWhether the bookmark is favourited.
descriptionNoLink description. Pass null to clear it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields 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"
    • removedInput schema / properties / author / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / author / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedInput schema / properties / createdAt / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • removedInput schema / properties / description / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / publisher / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / publisher / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / summary / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / summary / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / title / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / title / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Addedv1.0.1

TDQS

A3.6/5.0
Behavior3/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, and it does disclose the two most important traits: partial/patch-like update semantics ('only the fields you pass are modified') and the return value ('returns the updated bookmark'). It omits permissions, whether the update is reversible, and any conflict or rate-limit behavior — notable for a mutation 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.

Conciseness5/5

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

Three short sentences, each earning its place: purpose first, then the partial-update rule, then the return value. Nothing is redundant and the most decision-relevant constraint is front-loaded.

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

Completeness4/5

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

For an 11-parameter mutation with no output schema and no annotations, the description supplies the essentials an agent needs: what it mutates, the merge semantics, and that the updated object comes back. Auth requirements and error conditions are the remaining gaps.

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 every one of the 11 parameters, including null-to-clear semantics for title/author/summary/publisher/description, is documented in the schema. The description adds no parameter-specific detail, 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?

The description gives a specific verb and resource ("Update fields on an existing bookmark") that naturally separates it from update-highlight, update-list, and update-tag, and from create/delete/get-bookmark. It does not explicitly name any sibling or exclusion, which keeps it just 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?

The usage context is implied by 'existing bookmark' — the tool targets objects that already exist, so the agent knows to use create-bookmark otherwise. But there is no explicit when-to-use note, no precondition (e.g. required permissions), and no mention of which sibling to prefer for related updates.

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