Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

delete-highlight

Destructive

Delete a saved highlight by its ID to remove it from Karakeep, useful when a highlight is outdated, duplicate, or no longer needed.

Instructions

Delete a highlight by id.

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": {
      "highlightId": "<highlightId>"
    },
    "name": "delete-highlight"
  }
}

Input Schema

NameRequiredDescriptionDefault
highlightIdYesThe id of the highlight 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. Addedv0.33.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the deletion is permanent, what happens if the id does not exist (error vs silent success), or whether any permission is required.

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 waste and the resource and key front-loaded. It is efficient, though the terseness leaves no room for the behavioral context that a destructive tool warrants.

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

Completeness3/5

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

For a one-parameter destructive tool with annotations covering the safety profile and a fully documented schema, the essentials are present. It falls short on failure semantics and mutation effects, which an agent would want before invoking a delete.

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 coverage is 100% and the single highlightId parameter is fully documented in the schema, so the description carries no additional burden. The phrase 'by id' merely restates the parameter without adding format or sourcing detail, which is baseline-adequate.

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?

States a specific verb (delete) and resource (highlight) plus the lookup key (id), so the agent knows exactly what the tool acts on. It does not explicitly differentiate itself from sibling mutators like delete-bookmark or delete-list, though the resource name makes the distinction reasonably clear.

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 alternatives such as update-highlight, list-highlights, or get-highlight, and no preconditions stated. Usage must be inferred entirely from the name and the single required parameter.

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