Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

get-tag-bookmarks

List bookmarks that have a specific tag, with pagination, sorting, and optional full content, so you can browse or retrieve all items organized under that tag.

Instructions

List bookmarks that have a given tag, with pagination.

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-bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of bookmarks to return per page.
tagIdYesThe id of the tag whose bookmarks to fetch.
cursorNoCursor from a previous response to fetch the next page.
sortOrderNoSort order by creation date. Defaults to 'desc'.
includeContentNoIf true, include each bookmark's full content. Defaults to false.

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

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

With no annotations supplied, the description carries the full burden, and it does disclose that results are paginated, which is real behavioral context. It says nothing about read-only semantics, permission requirements, rate limits, or the default ordering, leaving meaningful gaps for a no-annotation tool.

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?

A single front-loaded sentence with no filler; the scope-defining qualifier ('that have a given tag') comes before the pagination note. 'With pagination' is slightly redundant given the cursor/limit parameters, keeping it just short of a 5.

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 five-parameter list tool with no output schema and no annotations, the description covers the essentials (scope plus pagination) but omits what a returned bookmark contains and how paging terminates. 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 including limit, cursor, sortOrder, and includeContent is already documented in the schema. The description only echoes pagination, adding no meaning beyond the structured fields; baseline 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?

The description names a specific verb ('List') and resource ('bookmarks that have a given tag'), so the operation is unambiguous. It does not distinguish itself from the closely related sibling get-list-bookmarks, which an agent could easily confuse with this tag-scoped listing.

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: the tag-scoped framing suggests calling it when you already have a tagId and want its bookmarks. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as search-bookmarks or get-list-bookmarks for other filtering axes.

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