Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Rename a bookmark or folder

rename

Changes a bookmark's name and optional URL, or a folder's name, to correct labels and keep browser bookmarks organized. Reports planned changes first by default.

Instructions

Changes the name (and optionally the URL) of a bookmark, or the name of a folder.

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": {
      "id": "<id>",
      "name": "<name>"
    },
    "name": "rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
urlNo
nameYes
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it omits the critical traits: the default dry-run preview-then-confirm workflow, the force flag and the risk that an open browser overwrites the file on close, and whether a conflicting name errors or overwrites. It does correctly signal the asymmetry that URL applies to bookmarks but not folders, which is real added meaning.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the primary action front-loaded and the optional URL clause clearly subordinated. Nothing is wasted, though the brevity tips toward under-specification for a mutation tool.

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

Completeness2/5

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

With six parameters, a destructive mutation, no annotations, and no output schema, the description should explain the safe dry-run-first flow and the force/browser-open hazard. It leaves both to the schema and never mentions that the default call performs no write, which is exactly the kind of detail an agent needs to avoid a surprising no-op or an unintended write.

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 description coverage is 50%: force, dry_run, and profile are documented in the schema, while id, name, and url are not. The description contributes the one non-obvious semantic — that url is optional and only meaningful for bookmarks — but adds nothing about id format or the name constraints beyond the schema's minLength.

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 concrete verb and resource: it changes the name of a bookmark or a folder, and optionally the URL of a bookmark. That distinguishes it from create_folder or add_bookmark, though it does not explicitly separate itself from move_bookmarks, which also mutates existing entries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says to call this instead of delete/recreate, nothing states prerequisites such as resolving the id first or picking a profile from list_profiles. The most consequential usage rule — that dry_run defaults to true so nothing is written on the first call — appears only in the schema, not in the description.

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