Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Check for broken links

check_links

Checks bookmarks over the network and reports dead links (404/410, DNS or connection failures) while listing bot-blocked sites as uncertain instead of dead.

Instructions

Visits bookmarks over the network and reports the ones that look dead (404/410, DNS failure, connection refused). Sites that block bots (401/403/429) are reported separately as "uncertain", never as dead.

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

Input Schema

NameRequiredDescriptionDefault
idsNoOnly check these bookmark ids.
maxNo
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.
folder_idNoOnly check this folder (recursively).
timeout_msNo
concurrencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well on the most important trait: it makes real network requests and classifies results with explicit rules (404/410, DNS failure, connection refused = dead; 401/403/429 = uncertain, never dead). It does not disclose duration, that it is non-mutating, or how concurrency/timeout affect the run.

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, front-loaded with the action and followed by the classification rule. Every clause carries information; nothing is redundant.

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 6-parameter, network-heavy tool with no annotations and no output schema, the description explains result classification but omits output shape (per-link status objects?), cost/time expectations, and the meaning of the tuning parameters. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: max, timeout_ms, and concurrency have no schema descriptions, and the description says nothing about any of the six parameters. It neither explains scoping via ids/folder_id nor the tradeoffs of timeout_ms and concurrency, so the undocumented half stays undocumented.

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?

States a specific verb and resource ('Visits bookmarks over the network and reports the ones that look dead') and further scopes the output into dead vs uncertain. No sibling performs network link checking, so the tool is unambiguously distinguishable from get_bookmarks or search_bookmarks.

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?

Usage is implied by the purpose: run it when you want to know which bookmarks are broken. There is no explicit when-to-use vs when-not guidance, no warning that this is slow/network-bound and should be scoped with ids or folder_id, and no mention of what to do with 'uncertain' results.

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