Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

delete-tag

Delete a tag by its ID without deleting bookmarks; the tag is only removed from any bookmarks that used it.

Instructions

Delete a tag by id. Bookmarks that had this tag are not deleted; the tag is just removed from them.

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": {
      "tagId": "<tagId>"
    },
    "name": "delete-tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagIdYesThe id of the tag to delete.

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

B3.3/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose the key side effect — bookmarks keep existing and only lose the tag association — which is genuinely valuable. But for a destructive operation it says nothing about irreversibility, permission requirements, or whether an in-use tag can be deleted; a clean statement that the deletion cannot be undone is the main missing piece.

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?

Two short sentences, front-loaded with the action and immediately followed by the one behavioral fact an agent needs. Nothing is redundant, though the second sentence could be tied more tightly to the sibling tools it contrasts with.

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 a single-parameter delete tool with no output schema, the definition covers the action, the target, and the main side effect, which is close to complete. The remaining gap is the lack of any statement about irreversibility or authorization, which matters for a destructive operation with no annotations.

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 there is only one parameter, so the schema already defines tagId completely. The description adds only "by id," which is no new information beyond the schema; it also does not say whether an id can be supplied as a name or slug.

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?

"Delete a tag by id" names a specific verb and resource, which separates it cleanly from delete-bookmark, delete-highlight, and delete-list in the sibling set. It stops short of stating how it differs from detach-tag-from-bookmark or update-tag, so the differentiation is mostly carried by the noun rather than explicit contrast.

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 second sentence implies the usage boundary: this destroys the tag object while merely unlinking it from bookmarks, which contrasts with detach-tag-from-bookmark that only unpairs one bookmark. However, it never explicitly says when to delete versus detach, nor mentions any prerequisite such as ownership or confirmation.

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