Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Restore a backup

restore_backup

Restore a browser bookmark backup from a previous snapshot, automatically backing up the current bookmarks first so the change can be undone.

Instructions

Puts a backup (from list_backups) back in place of the current bookmarks. The current state is backed up first, so this can be undone too.

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": {
      "backup_file": "<backup_file>"
    },
    "name": "restore_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoWrite even if the browser seems to be open. Avoid: an open browser overwrites the file when it closes.
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.
backup_fileYes

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, the description carries the full burden, and it does disclose the two most important traits: the restore replaces existing bookmarks and the prior state is snapshotted first, making it undoable. It omits the operational prerequisite that the browser should be closed (only surfaced inside the force parameter's schema description) and says nothing about failure behavior or permissions.

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 short sentences, zero filler, with the replace semantics front-loaded and the reversibility guarantee immediately after. Nothing is redundant with the name or title.

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-parameter mutation tool with no annotations and no output schema, this covers the essential semantic (what is replaced) and the essential risk mitigation (automatic pre-restore backup). Only the browser-must-be-closed caveat and post-call outcome are left to the parameter schema.

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 67% and the undocumented parameter is the required one, backup_file; the description compensates by tying it to list_backups, which the schema does not say. profile and force already carry their own descriptions, so the description correctly spends its words where the gap is.

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?

Uses a specific verb and resource ('Puts a backup ... back in place of the current bookmarks') and names the source tool list_backups, so the agent knows exactly what is swapped. It stops short of distinguishing itself from import_html or backup, which are the closest-looking siblings.

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?

Implies the workflow (obtain a backup_file via list_backups, then restore it) and reassures that the operation is reversible, which guides selection. It gives no explicit when-not conditions or comparison to import_html, so the guidance is implied rather than stated.

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