Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Create folders

create_folder

Creates bookmark folder paths, adding missing levels and defaulting to the bookmarks bar unless another top-level location is specified.

Instructions

Creates a folder path such as "Bookmarks bar/Work/Clients" (missing levels are created). Paths may start with "Bookmarks bar", "Other bookmarks" or "Mobile bookmarks"; otherwise the bookmarks bar is used.

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": {
      "path": "<path>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
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

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does disclose one important trait: intermediate levels are created automatically, and an unrecognized root prefix silently falls back to the bookmarks bar. It says nothing about the write target (the browser's Bookmarks file), the confirm-via-dry_run workflow, or the risk that an open browser overwrites changes, all of which are mutation-relevant behaviors left to the schema.

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?

Two tight sentences, front-loaded with the action and an example, then the root-prefix rule and its fallback. No filler, though the prefix rule could be shortened slightly.

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 file-mutating tool with no annotations and no output schema, the description covers path semantics well but omits the safety model (default dry_run, confirmation flow, browser-open hazard) and the optional profile selection. An agent can call it, but not without reading the schema to discover that nothing is written by default.

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 description coverage is 75%, so the baseline is 3, and the description exceeds it by defining the 'path' parameter's shape, allowed root prefixes, and default root behavior — semantics the bare string schema does not convey. It adds nothing about force, dry_run, or profile, but those are already documented in the schema.

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 opens with a specific verb+resource, 'Creates a folder path', and immediately shows a concrete example ("Bookmarks bar/Work/Clients"), so the agent knows exactly what operation is performed. It does not explicitly contrast itself with siblings like add_bookmark or sort_folder, which keeps it from a 5.

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?

Usage is implied rather than stated: the agent can infer this is the tool for creating nested folder structures because missing levels are auto-created. There is no when-not guidance, no mention of prerequisites such as needing a profile when multiple exist, and no pointer to alternatives for related tasks.

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