Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Bookmark statistics

stats

Summarize a browser bookmark profile’s totals, top domains, empty folders, and very old bookmarks before planning cleanup.

Instructions

Overview of a profile: totals, top domains, empty folders, very old bookmarks. Good first step before proposing a cleanup.

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

Input Schema

NameRequiredDescriptionDefault
topNo
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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the categories of information returned (totals, top domains, empty folders, old bookmarks), which is more than nothing. It never states that the operation is read-only, that it does not mutate bookmarks, or how the `top` limit bounds results, leaving the agent to infer the safety 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?

Two short sentences, with the substantive content (what is reported) front-loaded and the usage hint second. Every clause earns its place, though the phrasing is terse enough that it borders on under-specification rather than optimal density.

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?

The tool is simple (2 params, 0 required, flat schema, no output schema), and the description covers the general shape of what comes back. It omits the meaning of `top` and any detail about the return structure, so an agent knows roughly why to call it but not precisely how to interpret the count parameter.

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 coverage is 50%: `profile` is fully documented in the schema (including format and the single-profile optionality), while `top` has no schema description. The phrase "top domains" hints that `top` controls how many entries are returned, but the description never states that the parameter is a count limit, so it only marginally compensates for the gap.

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?

"Overview of a profile: totals, top domains, empty folders, very old bookmarks" states a specific resource (profile) and enumerates exactly what the tool reports, which disambiguates the vague name "stats". It does not explicitly contrast with siblings such as find_duplicates or check_links, 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 Guidelines4/5

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

"Good first step before proposing a cleanup" gives a clear usage context and implicitly positions the tool ahead of the cleanup siblings (remove_empty_folders, remove_duplicates, find_duplicates). It offers no explicit exclusions or named alternatives, so it is clear context without routing.

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