Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

get-tags

List tags with bookmark counts, then filter by name or attachment method and paginate results to organize bookmarks in Karakeep.

Instructions

List tags with their bookmark counts. Supports filtering and pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-tags"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order. 'relevance' requires nameContains. Defaults to 'usage'.
limitNoMaximum number of items to return per page.
cursorNoCursor from a previous response to fetch the next page.
attachedByNoFilter by how the tag was attached.
nameContainsNoFilter tags whose name contains this substring.

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.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that results are enriched with bookmark counts and that filtering/pagination are supported, but says nothing about default page size, ordering behavior (the schema's 'usage' default), or read-only safety beyond the implicit 'List' verb.

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?

Two short sentences with no waste, and the return-shape detail is front-loaded. Slight terseness means the second sentence borders on filler given the schema already documents filtering and pagination.

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 5-optional-parameter list tool with no output schema, the agent knows what it gets (tags with counts) and that it can paginate or filter, but the description never explains the response envelope or what distinguishes a tag's fields. Adequate but with clear gaps.

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%, so every parameter (sort, limit, cursor, attachedBy, nameContains) is already documented, including the 'relevance requires nameContains' constraint. The description's generic mention of filtering and pagination adds no meaning beyond the schema, so the baseline of 3 applies.

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 ('List tags') and adds the meaningful detail that each tag comes with its bookmark count, which distinguishes it from get-tag (single) and get-tag-bookmarks (bookmarks for a tag). It does not explicitly name a sibling, so it stops short of 5.

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?

'Supports filtering and pagination' hints at usage but gives no condition for choosing this over get-tag, get-tag-bookmarks, or get-lists. No when-not guidance or prerequisites are stated.

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