Skip to main content
Glama

search_bookmarks

Find saved bookmarks by searching titles, URLs, and descriptions, with optional folder filters and result limits to locate articles on specific topics or retrieve previously saved content.

Instructions

Find bookmarks by searching through titles, URLs, and descriptions. Supports optional filtering by folder (use "unread", "archive", "starred", or a specific folder_id) and result limits. Useful for discovering articles on specific topics or finding previously saved content.

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": {
      "query": "<query>"
    },
    "name": "search_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 25)
queryYesSearch query
folderNoOptional folder to search in (unread, archive, starred, or folder_id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it conveys that this is a read/find operation and documents the folder-filter special values, but it omits result ordering, matching semantics (substring vs token), and what a result record contains.

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?

Three tight sentences, front-loaded with the core action and searchable fields, then filters, then intent. The final sentence is somewhat expendable filler but does not bloat the definition.

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 three simple parameters and no output schema, the description covers the call mechanics adequately, but it never indicates the shape of returned results or how limits interact with paging, leaving a real gap for a search tool.

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 the baseline is 3; the description repeats the folder enum values and the notion of result limits without adding syntax, range, or default behavior beyond what the schema already states.

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: 'Find bookmarks by searching through titles, URLs, and descriptions,' and names the searched fields, which separates it from a plain listing tool like list_bookmarks. It doesn't explicitly name a sibling to contrast with, so it falls just short of the top score.

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?

Offers use-case framing ('discovering articles on specific topics or finding previously saved content'), which implies when to reach for it, but gives no explicit when-not guidance and never points to list_bookmarks for unfiltered browsing or to the bulk action siblings.

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