Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

list_bookmarks

Retrieve all bookmarks from a specified browser along with their folder paths, so you can inspect or organize saved links by location.

Instructions

All bookmarks with folder paths.

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>"
    },
    "name": "list_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
browserYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and discloses almost nothing: no hint that this is a safe read, no scope (which browser/profile), no pagination or ordering, no note on what happens if no bookmarks exist. The only behavioral signal is that folder paths are included in results.

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

Conciseness2/5

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

Six words is not conciseness but under-specification; there is no wasted text because there is barely any text. It reads as a label rather than a front-loaded description, so efficiency comes at the cost of usefulness.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but for a one-required-parameter tool with no annotations the description should at minimum identify the browser scoping and the read-only nature. Neither is present, leaving the definition materially incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter "browser" has 0% schema description coverage, and the description never mentions it. An agent gets no information about what values are accepted, whether it is a name, ID, or index, or that it is mandatory.

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

Purpose2/5

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

The description is a noun fragment ("All bookmarks with folder paths") that essentially restates the tool name list_bookmarks, adding only the detail that folder paths are included. There is no verb and no statement of what operation is performed, so an agent must infer retrieval from the name alone.

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?

There is no when-to-use guidance, no exclusion criteria, and no reference to alternatives such as add_bookmark or list_browsers. The word "All" hints at a complete listing versus a filtered one, but that is inference rather than stated guidance.

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