bookmark-mcp

Search bookmarks

search_bookmarks

Read-only

Find bookmarks by text, tag, or read status. List recent bookmarks when no criteria are specified.

Instructions

Search the reading list by free text, tag, and/or read status. Call without arguments to list the most recent bookmarks.

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": "search_bookmarks"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Only return bookmarks carrying this tag
`limit`	No	Maximum results to return
`query`	No	Case-insensitive text matched against title, URL, and notes. Omit to list all.
`unreadOnly`	No	Only return unread bookmarks

Output Schema

Name	Required	Description	Default
`total`	Yes	Number of bookmarks returned
`bookmarks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 25, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, consistent with description. Description adds the behavior of listing most recent bookmarks when called without arguments, but otherwise does not elaborate on return format, pagination, or other behavioral details beyond what annotations provide.

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?

Two sentences: first states purpose and search dimensions, second notes the default behavior. Very efficient, no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values are covered. Description covers all intended uses (search, list) and parameter categories. Given low complexity and good schema support, it is completely adequate.

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 has 100% coverage with descriptions for all 4 parameters. The description summarizes them concisely but adds no new meaning beyond the schema.

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?

Description clearly states verb 'search' and resource 'reading list', specifies searchable dimensions (free text, tag, read status) and a default behavior (list recent). It distinguishes from siblings that add, delete, or mark read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description explicitly states when to use (search by criteria or list recent) but does not directly mention when not to use or point to siblings as alternatives. The context of sibling tools implies alternatives, but the description itself lacks explicit guidance.

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

Deploy Server