Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

remove-bookmark-from-list

Remove a bookmark from a specific list by providing the list ID and bookmark ID. Use this to organize or clean up list contents.

Instructions

Remove a bookmark from 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": "remove-bookmark-from-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe listId to remove the bookmark from.
bookmarkIdYesThe bookmarkId to remove.

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.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It does not disclose whether the operation is idempotent, what error occurs if the bookmark is not in the list, whether the list itself is preserved, or what permissions are required for a mutation. Only the bare mutation intent is conveyed.

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 efficient sentence with no filler or redundancy. Its brevity is appropriate in form, though it leans toward under-specification rather than optimal density.

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 should do more: explain failure behavior, return values, and side effects. Given the tool's relative simplicity the gap is moderate, but the definition is not sufficient for an agent to call it confidently in edge cases.

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 both listId and bookmarkId are documented in the input schema, establishing a baseline of 3. The description adds no further meaning such as ID format, whether IDs are opaque, or how to obtain them, so it neither compensates nor detracts.

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 states a concrete verb and resource ('remove a bookmark from a list'), but it essentially restates the tool name with no additional scoping or differentiation from siblings like add-bookmark-to-list or delete-list. An agent can tell what it does, but the wording is tautological rather than clarifying.

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 note on prerequisites (e.g., bookmark must already be in the list), and no mention of alternatives such as delete-bookmark or add-bookmark-to-list. The agent must infer the usage 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.