Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Back up bookmarks

backup

Creates a copy of the selected browser profile's bookmarks file, preserving current bookmarks before edits or for later recovery.

Instructions

Makes a copy of the profile bookmarks file now. (Every write tool also does this automatically.)

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key behavioral trait that this duplicates automatic write-tool behavior, which is valuable. However, it says nothing about where the backup is written, whether it overwrites a prior backup, retention, or what the call returns (no output schema exists), leaving meaningful gaps for a side-effecting tool.

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 action front-loaded and the important caveat immediately after it. Nothing could be removed without losing information.

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 single optional-parameter tool with a fully described schema, the definition covers what it does and when it is redundant. The one remaining hole is the return value—no output schema exists and the description does not say whether a backup path or confirmation comes back.

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

Parameters3/5

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

Schema coverage is 100% and the profile parameter already documents both the id format with examples and the full-path alternative, so the schema does the heavy lifting. The description only implies that "profile bookmarks file" is the target, adding no syntax or selection guidance beyond the schema. Baseline 3 is appropriate.

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?

"Makes a copy of the profile bookmarks file now" names a specific verb (copy) and resource (bookmarks file), and the parenthetical distinguishes it from the write siblings by noting they back up automatically. It stops short of naming restore_backup or list_backups, but the operation itself is unambiguous.

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?

"Now" plus "every write tool also does this automatically" tells the agent this is a rarely-needed manual snapshot rather than a routine step. That is a genuine usage signal, though it never states prerequisites (does the profile need to exist?) or points to list_backups/restore_backup as the follow-on tools.

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