Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

attach-tag-to-bookmark

Attach one or more tags to a specific bookmark by providing its bookmark ID and tag names.

Instructions

Attach a tag to a bookmark.

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": {
      "bookmarkId": "<bookmarkId>",
      "tagsToAttach": "<tagsToAttach>"
    },
    "name": "attach-tag-to-bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmarkIdYesThe bookmarkId to attach the tag to.
tagsToAttachYesThe tag names to attach.

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. Changed1 schema field changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

C2.9/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 behavioral burden, yet it discloses nothing beyond the bare action. It does not say whether tag names must already exist, whether unknown tags are created automatically, whether re-attaching an existing tag is idempotent or an error, or what permissions are required — all critical for a write operation.

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?

The single short sentence is front-loaded with the action and contains no filler. It is efficient, though the extreme brevity borders on under-specification rather than economy.

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 two-parameter, flat-schema tool with full schema coverage and no output schema, the essentials of the call are documented. However, the most consequential unknown — whether attaching a non-existent tag name creates it or fails — is left entirely unaddressed for a mutation tool 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%, with both bookmarkId and tagsToAttach documented inline, including that tagsToAttach is a list of tag names. The description adds no meaning beyond that, so the baseline of 3 applies; it notably does not clarify whether those names must map to existing tags.

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 two resources: 'Attach a tag to a bookmark.' This clearly distinguishes it from detach-tag-from-bookmark and from tag-CRUD siblings like create-tag or update-tag without needing to open the schema.

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 tool versus alternatives, no preconditions, and no exclusions. The agent must infer from the name alone that this is the mutation path for linking an existing tag to a bookmark and that detach-tag-from-bookmark is the inverse.

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