Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Find duplicate bookmarks

find_duplicates

Groups bookmarks that point to the same page while ignoring http/https, www, trailing slashes, fragments, and utm_* tracking parameters.

Instructions

Groups bookmarks that point to the same page (ignores http/https, www, trailing slash, #fragment and utm_* tracking parameters).

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

Input Schema

NameRequiredDescriptionDefault
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.3/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 a genuinely important behavioral trait: the URL normalization rules (http/https, www, trailing slash, #fragment, utm_*). However, it does not state that the operation is read-only/non-destructive, whether it scans the whole bookmark file or a subset, or what the grouped results look like.

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?

One tightly written sentence with the core action front-loaded and the normalization qualifiers in a subordinate parenthetical. No filler, and the caveats that affect correctness are stated compactly.

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 single-optional-parameter tool this is close to adequate, and the normalization rules cover the main correctness concern. But with no annotations and no output schema, an agent still does not know the safety profile or the shape of the returned groups (e.g., grouped lists keyed by canonical URL), which matters for chaining into remove_duplicates.

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 single 'profile' parameter already documents its format, example values, and the fact that it is optional when only one profile exists. The description adds nothing about the parameter, so the schema does all the work and the baseline of 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 ('Groups') and resource ('bookmarks that point to the same page'), and the parenthetical pinpoints exactly what counts as 'the same page'. It is unambiguous what the tool produces, though it never explicitly contrasts itself with the very similarly named sibling remove_duplicates, so an agent must infer the read-only/grouping-vs-removal distinction.

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, no prerequisites, and no mention of alternatives such as remove_duplicates. The natural workflow (find duplicates, then remove them) is left entirely to inference from the tool name.

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