Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Sort a folder

sort_folder

Sort folder contents alphabetically or by URL or date added, with folders first and optional recursion into subfolders. Keeps browser bookmarks organized while leaving the bookmarks bar untouched.

Instructions

Sorts the contents of a folder alphabetically, folders first. Use recursive to sort every subfolder too. Without folder_id, sorts everything except the bookmarks bar top level (whose order users usually choose by hand).

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

Input Schema

NameRequiredDescriptionDefault
byNoname
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.
folder_idNo
recursiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 non-obvious behavior — folders sort before files, and the top-level bookmarks bar is excluded by default. However it never says the tool rewrites the Bookmarks file on disk, that it defaults to a no-write preview, or that an open browser can clobber the result, all of which are meaningful traits for a mutating operation.

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?

Three short sentences, front-loaded with the core behavior and then the two scoping modifiers. Every clause conveys information not already in the schema; nothing is padding.

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 6-parameter, no-annotation, no-output-schema tool, the description nails ordering and scope but omits the dry-run-first confirmation loop and the risks around force and an open browser, relying entirely on the schema for those. Adequate but not complete for a file-writing operation.

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?

At 50% schema coverage the description does real work: it explains folder_id semantics (absent = everything but the top-level bar) and recursive (subfolders included), neither of which the schema documents. It is silent on the 'by' enum's url and date_added options, leaving the reader with only the alphabetical default, and says nothing about force or profile.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (sorts a folder), plus the concrete ordering rule ('alphabetically, folders first'). No sibling in the list performs sorting, so there is nothing to disambiguate, and the scope rule for folder_id is spelled out immediately.

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?

Gives real when-to-use guidance: set recursive to sweep subfolders, and omit folder_id to sort everything except the bookmarks bar (with the rationale that users hand-order it). It does not mention the dry-run-then-confirm workflow, which is the main invocation caveat, but that lives in the schema.

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