Skip to main content
Glama
karakeep-app

Karakeep MCP server

by karakeep-app

search-bookmarks

Find bookmarks using full-text, semantic, or hybrid search. Use qualifiers for tags, dates, favorites, and more to narrow results.

Instructions

Search for bookmarks matching a specific query using full-text, semantic, or hybrid search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe number of results to return in a single query.
queryYes By default, this will do a full-text search, but you can also use qualifiers to filter the results. You can search bookmarks using specific qualifiers. is:fav finds favorited bookmarks, is:archived searches archived bookmarks, is:tagged finds those with tags, is:inlist finds those in lists, and is:link, is:text, and is:media filter by bookmark type. url:<value> searches for URL substrings, #<tag> searches for bookmarks with a specific tag, list:<name> searches for bookmarks in a specific list given its name (without the icon), after:<date> finds bookmarks created on or after a date (YYYY-MM-DD), and before:<date> finds bookmarks created on or before a date (YYYY-MM-DD). If you need to pass names with spaces, you can quote them with double quotes. If you want to negate a qualifier, prefix it with a minus sign. ## Examples: ### Find favorited bookmarks from 2023 that are tagged "important" is:fav after:2023-01-01 before:2023-12-31 #important ### Find archived bookmarks that are either in "reading" list or tagged "work" is:archived and (list:reading or #work) ### Combine text search with qualifiers machine learning is:fav
sortOrderNoSort by relevance or creation date. Defaults to relevance.
nextCursorNoThe next cursor to use for pagination. The value for this is returned from a previous call to this tool.
searchModeNoSearch strategy. 'fts' uses full-text search, 'semantic' uses embeddings, and 'hybrid' combines both. Semantic and hybrid modes only support relevance sorting. Defaults to 'fts'.fts
Behavior2/5

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

No annotations are provided, so the description carries the full burden. However, it only restates the search modes already present in the searchMode schema enumeration; it does not disclose whether the operation is read-only, any side effects, return format, or pagination behavior. This adds minimal behavioral context beyond the structured schema.

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?

The description is a single, front-loaded sentence that efficiently conveys the core action and search modes without extraneous information. Every word earns its place.

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?

With 5 parameters, no output schema, and no annotations, the description is sparse. The schema provides rich parameter details, but the description does not mention return values, pagination, or operational context such as read-only guarantees. It is minimally complete for understanding the tool's purpose but lacks a full picture for a new agent.

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%, and the query parameter includes extensive documentation of qualifiers and examples. The description adds no additional parameter semantics, so baseline 3 is appropriate given the schema's completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Search'), the resource ('bookmarks'), and the method ('full-text, semantic, or hybrid search'). This distinguishes it from sibling tools like get-bookmark or get-list-bookmarks, which retrieve specific bookmarks or list contents rather than performing query-based search.

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?

The description implies usage for query-based search via 'matching a specific query', but it does not explicitly compare to alternatives or state when not to use this tool. There is no mention of exclusions or alternative tools, so guidance remains largely implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karakeep-app/karakeep'

If you have feedback or need assistance with the MCP directory API, please join our Discord server