Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

update-tag

Rename an existing tag by providing its ID and a new name; the server normalizes the name for consistent tagging.

Instructions

Rename a tag. The new name is normalized by the server.

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": "<name>"
    },
    "name": "update-tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew name for the tag. Will be normalized by the server.
tagIdYesThe id of the tag to update.

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.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does little beyond noting server-side normalization of the new name. It omits whether the rename propagates to all tagged bookmarks, whether duplicate names are rejected, and what errors occur for an unknown tagId.

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?

Two short sentences with the operation stated first and the notable server-side side effect second; nothing is padded or buried.

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 simple two-parameter mutation with a fully documented schema, the definition is close to adequate, but with no annotations and no output schema the agent still lacks the side-effect and failure-mode information that matters for a write operation.

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 both parameters are described in the schema, so the baseline is 3. The description's normalization note duplicates the schema's own text for "name" rather than adding new meaning such as format rules, length limits, or allowed characters.

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?

The description states a specific verb and resource ("Rename a tag") that matches the two-parameter schema exactly, so an agent knows this is a rename-only operation and not a general update. It does not explicitly contrast itself with siblings like update-list or delete-tag, relying on the resource noun alone for differentiation.

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 when-to-use guidance: nothing says when to rename versus create/delete a tag, nor any precondition such as the tag existing or the caller having ownership. The only guidance is implied by the verb "Rename".

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