Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Search bookmarks

search_bookmarks

Find bookmarks by name, URL, or folder with case-insensitive queries across browser profiles, so you can locate and organize saved pages.

Instructions

Searches bookmark names, URLs and folder names (case-insensitive).

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
limitNo
queryYes
profileNoProfile id from list_profiles (e.g. "chrome:Default", "edge:Profile 1") or the full path to a Bookmarks file. Optional when only one profile exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden; it does disclose case-insensitive matching and the field set searched, which is genuine behavioral context. It says nothing about read-only/side effects, result ordering, how 'limit' truncates results, or what happens with a missing/invalid profile.

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 tight sentence with zero filler and the matching scope front-loaded. It is arguably under-specified rather than over-long, so efficiency is not the problem.

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

Completeness2/5

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

No output schema and no annotations, yet the description omits return shape, ordering, and how the default 200 / max 1000 limit affects results. For a search tool with three parameters this leaves the agent guessing on non-trivial behavior.

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 only 33%, so the description must compensate; it does add real meaning for 'query' by naming the three fields matched and the case-insensitive match rule. 'limit' and 'profile' semantics remain entirely schema-only, and no query syntax (multi-word, partial match) is explained.

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 (Searches) and the exact fields matched (bookmark names, URLs, folder names), which tells an agent what the tool returns hits on. It does not distinguish itself from sibling get_bookmarks, so it stops short of a 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?

There is no when-to-use guidance and no mention of alternatives such as get_bookmarks for unfiltered listing or find_duplicates. The only implicit signal is that this tool is for text lookup, which the agent must infer.

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