Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Export bookmarks to HTML

export_html

Saves all bookmarks or a single folder as a standard HTML file for import into Chrome, Edge, Firefox, Safari, or other browsers, without altering the current browser.

Instructions

Saves the bookmarks (all, or one folder) as a standard bookmarks .html file that any browser can import (Chrome, Edge, Firefox, Safari, Opera…). Does not change the browser.

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

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.
folder_idNoOnly export this folder.
output_pathNoWhere to save. Default: Desktop (or home) / bookmarks-<browser>-<profile>-<date>.html

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 does disclose the key safety fact: 'Does not change the browser,' so the agent knows this is a non-mutating read of bookmark data. It says nothing about whether an existing file at output_path is overwritten, whether the target directory must exist, or what happens if the profile is absent — meaningful gaps for a tool that writes to disk.

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 the output artifact, with the non-mutation caveat appended. Every clause earns its place and nothing is padded.

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 three-optional-parameter tool with full schema documentation and no output schema, this covers the essentials: what is produced, that it is broadly importable, and that nothing is mutated. The only real omission is file-overwrite/collision behavior, which the schema's default-naming note partially mitigates.

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 description coverage is 100%, so the baseline is 3; the description adds a little by clarifying the folder_id scope ('all, or one folder'), which frames that partial export is supported. It adds no detail on profile resolution or output_path format beyond what the schema already states.

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 gives a specific verb and resource — saving bookmarks (all or one folder) as a standard bookmarks .html file — and names the target consumers (Chrome, Edge, Firefox, Safari, Opera). It does not explicitly contrast itself with siblings like import_html, preview_html, or backup, so the agent must infer the distinction from the names.

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 only implied by the name and the phrase 'any browser can import' — the reader infers this is for migrating or archiving bookmarks out of the browser. There is no explicit when-to-use statement, no exclusion (e.g. use backup for full restore-able snapshots, preview_html to inspect first), and no prerequisites.

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