Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Import bookmarks from HTML

import_html

Load bookmarks from an exported HTML file into a browser profile: append them to a folder or replace current bookmarks, with a dry-run preview before writing.

Instructions

Loads a bookmarks .html file (exported from any browser or from the web tool) into a profile. mode "append": everything goes inside a new folder (default "Imported") in Other bookmarks. mode "replace": the current bookmarks are removed and the file becomes the new bookmarks (its toolbar folder goes to the bookmarks bar). Dry run by default.

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

Input Schema

NameRequiredDescriptionDefault
modeNoappend
forceNoWrite even if the browser seems to be open. Avoid: an open browser overwrites the file when it closes.
dry_runNoWhen true (default) nothing is written; the tool only reports what would change. Show that to the user and call again with dry_run=false after they confirm.
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.
input_pathYes
folder_nameNoFolder used by append mode.Imported
skip_existingNoAppend mode: skip pages that are already bookmarked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/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 and does well: it discloses that replace mode destructively removes existing bookmarks, where each mode places content, and that dry run is the default. It omits related safety context such as whether a backup is made first, and the force/open-browser hazard is only documented in the schema.

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?

Dense but zero waste: the core action and destination come first, then each mode is spelled out, then the dry-run default lands as the final, decision-relevant fact. Nothing is repeated from the schema.

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

Completeness4/5

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

For a destructive, 7-parameter import with no annotations and no output schema, the description covers the essentials an agent needs to act safely and to choose a mode. It could say more about the profile-selection requirement and what the dry-run report contains, but the schema fills those gaps.

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

Parameters4/5

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

Schema coverage is 71%, and the description meaningfully extends it by explaining what mode values actually do to the profile and how folder_name's default 'Imported' applies only in append mode. It adds nothing for force, skip_existing, profile, or input_path, though those are largely covered by schema descriptions.

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 ('Loads a bookmarks .html file ... into a profile') plus the two operating modes, which implicitly separates it from export_html and preview_html. It does not name a sibling explicitly, so it falls short of the top mark.

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?

Clearly explains that append puts everything in a new folder under Other bookmarks while replace wipes current bookmarks, and that dry run is the default so the agent should report and re-call after confirmation. It does not say when to prefer this over preview_html or when to skip it entirely.

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