Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Add a bookmark

add_bookmark

Adds a bookmark to a chosen folder by ID or path, creating the folder when missing so saved links stay organized.

Instructions

Adds a bookmark to a folder (by id or path, created if missing).

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": {
      "url": "<url>"
    },
    "name": "add_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameNo
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
folder_pathNoUsed when folder_id is not given. Defaults to "Bookmarks bar".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden, and it does disclose one important side effect: the target folder is created if missing. It omits the write-safety profile entirely — that dry_run defaults to true and requires a second call after user confirmation, and that force risks the open browser overwriting the file — leaving those to the schema alone.

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?

One compact sentence with the core action and the auto-create caveat front-loaded; nothing is redundant. It is arguably over-compressed for a seven-parameter tool with a dry-run default, but every word present earns its place.

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 mutation tool with seven parameters and no annotations or output schema, a single sentence is thin. The schema descriptions rescue the critical dry_run and force semantics, but the description itself never signals that the default call writes nothing, which is the single most important fact for correct invocation.

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 57%, so some compensation is needed. The description adds real meaning beyond the schema by stating that folder_id/folder_path are alternatives and that a missing folder is created, but it says nothing about url, name, profile, force, or dry_run, leaving the highest-risk parameters undocumented in prose.

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?

States a specific verb and resource ("Adds a bookmark") plus the target container and how it is resolved ("to a folder (by id or path, created if missing)"). This clearly separates it from read-only siblings like get_bookmarks or search_bookmarks, but it does not explicitly contrast with import_html or create_folder, which an agent might otherwise consider.

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?

No guidance on when to use this instead of import_html, create_folder, or move_bookmarks, and no mention of the confirmation workflow implied by dry_run defaulting to true. The only conditional information (folder_path used when folder_id is absent) is parameter-level, not usage-level.

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