Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

detach-tag-from-bookmark

Detach one or more tags from a bookmark by specifying its ID and the tag names to remove.

Instructions

Detach a tag from a 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>",
      "tagsToDetach": "<tagsToDetach>"
    },
    "name": "detach-tag-from-bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmarkIdYesThe bookmarkId to detach the tag from.
tagsToDetachYesThe tag names to detach.

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?

No annotations and no output schema, so the description carries the full burden and discloses almost nothing. It does not state whether the tag itself survives (critical distinction from delete-tag), whether the call is idempotent when the tag is not attached, what permissions are needed, or what is returned.

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 filler or redundant phrasing, and the action is front-loaded in the verb. It is efficient, though efficiency here partly reflects under-specification rather than disciplined editing.

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?

This is a mutating tool with no annotations and no output schema, and the description supplies none of the compensating context: reversibility, effect on the underlying tag entity, behavior on missing tags, or return shape. For a destructive relationship change, this is well short of what an agent needs.

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%: bookmarkId and tagsToDetach are both documented in the schema, including that tagsToDetach takes tag names. The description adds no meaning beyond that, so the baseline 3 applies.

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 sentence names a concrete verb (detach) and both resources (tag, bookmark), so the operation is unambiguous. However, it is essentially the tool name rendered as prose, and it draws no distinction from siblings such as attach-tag-to-bookmark or delete-tag, which an agent must choose between.

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 attach-tag-to-bookmark (the inverse) or delete-tag (which presumably removes the tag globally). No prerequisites or context are given, leaving the agent to infer the distinction from sibling names alone.

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