Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Move bookmarks or folders

move_bookmarks

Moves selected bookmarks into a target folder by ID or path, creating the folder when missing. Reorganize bookmarks in bulk, with a dry-run preview by default.

Instructions

Moves items into a folder. Give target_folder_id, or target_path (e.g. "Bookmarks bar/Study/Python") which is created when missing. For a big reorganization, call this once per destination folder with all the ids that go there.

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": {
      "ids": "<ids>"
    },
    "name": "move_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
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.
target_pathNo
target_folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 disclosure burden. It usefully reveals one non-obvious side effect — target_path is created when missing — but says nothing about the dry_run default, the force/open-browser hazard, or confirmation flow, all of which are pushed into schema parameter text rather than the description.

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?

Three short sentences, front-loaded with the action, then the targeting choice, then the batching tip. The inline path example is functional rather than filler; little could be trimmed without losing guidance.

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

Completeness3/5

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

For a six-parameter mutation tool with no annotations and no output schema, the description covers targeting and batching but leaves the safety story (dry_run default, force semantics, multi-profile requirement) entirely to the schema. It is adequate but not complete for an operation that rewrites the bookmarks file.

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 50%, and the description does compensate for the undocumented target_path (path syntax plus auto-creation) and implies ids is a batch list. However target_folder_id is only named, not explained (format/source, e.g. from get_bookmarks), and no hint is given about profile selection.

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?

"Moves items into a folder" is a specific verb+resource pair, and the mention of folders, ids, and target paths makes the scope concrete. It doesn't explicitly contrast with siblings like rename or create_folder, 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?

It states the two targeting modes (target_folder_id vs target_path) and gives a concrete batching rule: one call per destination folder with all ids that belong there. What's missing is any exclusion guidance (e.g., when to use rename instead, or whether this can move folders as well as bookmarks, despite the title saying 'or folders').

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