Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

update-list

Modify an existing Karakeep list by changing only the fields you specify, including name, icon, description, visibility, parent, and smart-list query.

Instructions

Update a list. Only the fields you pass are changed. Length caps and smart-list query rules come from the shared list schema.

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": "update-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoNew emoji icon for the list.
nameNoNew name for the list.
queryNoNew smart-list query. Only meaningful for smart lists.
listIdYesThe id of the list to update.
publicNoWhether the list is publicly accessible.
parentIdNoNew parent list id. Pass null to move to the root.
descriptionNoNew description for the list. Pass null to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields 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"
    • removedInput schema / properties / parentId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / parentId / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does usefully disclose partial-update semantics ('Only the fields you pass are changed'), which is real behavioral value. However it says nothing about permissions, reversibility, failure modes, or what the mutation returns, and it delegates validation rules to an unspecified 'shared list schema' rather than stating them.

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?

Three tight, front-loaded sentences with no filler. The final sentence is somewhat hand-wavy, deferring constraints to an external 'shared list schema' the agent may not have access to.

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 7-parameter mutation tool with no annotations and no output schema, the definition covers the partial-update contract but omits permissions, error behavior, and result shape. Adequate, but leaves real gaps an agent would want filled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning by explaining that unmentioned fields are left untouched and that smart-list query rules govern the 'query' parameter. That is genuinely useful semantic framing beyond the per-parameter descriptions.

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 and resource ('Update a list') that is unambiguous against siblings like update-bookmark or update-tag. It does not explicitly differentiate from create-list/get-lists, but the intent is clear.

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?

Usage is implied by the 'update' verb and the partial-update rule, but there is no explicit guidance on when to use this versus create-list or other mutators, and no prerequisites such as required permissions or ownership.

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