Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

add_bookmark

Adds a single bookmark to a chosen browser on explicit user request, using the provided URL, title, and optional folder.

Instructions

Add one bookmark. ONLY on explicit user request.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
titleYes
folderNo
browserYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses only a usage constraint. It says nothing about duplicate handling, required browser permissions, whether folder is created if missing, or what the mutation does to browser state — all critical for a write operation.

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

Conciseness3/5

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

Two short sentences, front-loaded, with zero filler. The brevity is efficient but tips into under-specification rather than earned conciseness for a four-parameter mutation tool.

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?

The presence of an output schema means return values need not be described, and the explicit-request gate is stated. Still, an unannotated mutation tool with four undocumented parameters leaves an agent without enough information to fill browser and folder correctly.

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 0% across four parameters, so the description should compensate; it only implies that url and title belong to a single bookmark and says nothing about browser or the folder array semantics. Placeholder text at 0% coverage leaves required params like browser and folder unexplained.

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 ("Add one bookmark"), and the singular "one" conveys per-call granularity. It does not differentiate from the sibling list_bookmarks or explain how this relates to import_state, so an agent gets the action but no sibling contrast.

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?

"ONLY on explicit user request" is a real gating condition that constrains when the agent may call it, which is more than most definitions offer. However, it names no alternative and gives no guidance on choosing between this and bulk operations like import_state or export_state.

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