Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

get-tag

Retrieve a single tag by its ID, including how many bookmarks use it. Use it to look up tag details and bookmark counts.

Instructions

Retrieve a single tag by id, including its bookmark counts.

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": "get-tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagIdYesThe id of the tag to retrieve.

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

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that bookmark counts are included in the response, which goes beyond a bare read statement, but says nothing about behavior when the id does not exist (error vs empty) or about authentication scoping.

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?

One short sentence, front-loaded with the verb and resource, with no redundant or filler wording.

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 trivial single-parameter read tool with no output schema, this is close to sufficient: it names the lookup key and hints at the return content. Only the not-found behavior is left unstated.

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?

Only one parameter (tagId) with 100% schema description coverage, so the schema already explains it. The description's 'by id' merely restates that, adding no format or constraint detail beyond the schema.

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 (retrieve) and resource (single tag) and adds the payload detail 'including its bookmark counts'. It is distinguishable from get-tags by the singular 'a single tag by id', though it never names the plural sibling explicitly.

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 only implied by the phrase 'single tag by id' — an agent can infer this is the direct-lookup tool versus get-tags or get-tag-bookmarks, but there is no explicit when-to-use or when-not-to-use guidance.

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