Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Preview an HTML bookmarks file

preview_html

Reads a bookmarks HTML file and displays its folder structure and counts without importing, so you can inspect it before adding bookmarks.

Instructions

Reads a bookmarks .html file and shows its folder structure and counts without importing anything.

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": {
      "input_path": "<input_path>"
    },
    "name": "preview_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_linesNo
input_pathYes

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?

No annotations are provided, so the description carries the full burden; it does state the key behavioral fact that nothing is imported or mutated, which is the most important disclosure for this tool. It omits how truncation works (max_lines default 300, cap 3000), what happens on a missing/malformed file, and whether profiles or existing bookmarks are touched.

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 sentence, front-loaded with the action and result, with zero filler. The non-importing caveat is placed at the end where it reads as a qualifier rather than burying the primary purpose.

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 two-parameter read-only preview tool with no output schema and no annotations, the description covers purpose and non-mutation well but leaves the preview's limits unstated. An agent cannot tell how much of a large file will be shown or what the response looks like in truncated cases.

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 description coverage is 0% for both parameters, so the description must compensate and does not. input_path is never described (absolute vs relative, expected extension) and max_lines is never mentioned, so its truncation role is entirely undocumented even though its default and bounds appear in the schema.

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 and resource ('Reads a bookmarks .html file') and the output shape ('shows its folder structure and counts'). The clause 'without importing anything' implicitly separates it from import_html, though it never names that sibling directly.

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?

The phrase 'without importing anything' signals a safe dry-run usage context, letting an agent infer this precedes a real import. However, there is no explicit when-to-use/when-not guidance or named alternative (e.g. import_html, get_bookmarks) to confirm the routing decision.

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