Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

delete-list

Deletes a list by ID without removing its bookmarks; any child lists are moved to root level, so re-parent children first if you need a different tree structure.

Instructions

Delete a list by id. Bookmarks inside the list are not deleted. Child lists are also not deleted. Any child lists become root-level lists (their parentId is set to null). If that isn't the tree change you want, move or re-parent the children before calling this.

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>"
    },
    "name": "delete-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe id of the list 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

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does it well: it discloses the non-cascading delete of bookmarks, the re-parenting of child lists to parentId=null, and the alternative action. It does not state whether the deletion is permanent/irreversible or what permissions are required, which are the notable remaining gaps for a destructive operation.

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?

Four short sentences, front-loaded with the action, then side effects, then the remediation path. No filler and no redundancy; every sentence changes what the agent knows or does.

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 one-parameter destructive tool with no annotations and no output schema, the definition covers the critical unknowns: what is preserved, what is re-parented, and how to avoid the re-parenting. Irreversibility and authorization behavior are the only meaningful omissions.

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?

There is a single parameter with 100% schema description coverage stating 'The id of the list to delete.' The description's 'by id' adds no semantics beyond that, so the schema does the work and the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource tied to a key: 'Delete a list by id.' It then immediately scopes the operation by clarifying what is NOT affected (bookmarks, child lists), which makes the blast radius unambiguous and distinguishes it from sibling delete tools like delete-bookmark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear conditional: child lists become root-level, and 'If that isn't the tree change you want, move or re-parent the children before calling this.' That is real pre-call guidance rather than a restatement of purpose. It stops short of naming a specific sibling to use for re-parenting, which keeps it from a 5.

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