Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

List browser profiles

list_profiles

Lists every Chromium-based browser profile with bookmarks on this computer, including bookmark counts and whether the browser is currently open.

Instructions

Finds every Chromium-based browser profile (Chrome, Edge, Brave, Vivaldi, Opera, Chromium) on this computer that has bookmarks, with counts and whether the browser is open.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the scope (Chromium-based browsers only, so Firefox is out), the filtering rule (profiles without bookmarks are omitted), and part of the return payload (counts, browser-open state). It never states that the operation is read-only or whether it scans the filesystem and how expensive that is.

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?

A single front-loaded sentence with no filler. The parenthetical browser list earns its place by defining the supported scope, and the result content is stated compactly at the end.

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

Completeness4/5

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

For a simple zero-parameter read tool with no output schema, the description covers scope, filtering, and partial return content. The remaining gap is that it doesn't say what identifies each profile (name, path, browser, id), which an agent needs in order to chain into the bookmark tools that follow.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a no-param tool applies. The description correctly implies the tool is called with no arguments and returns a filtered enumeration.

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 uses a specific verb ('Finds') and a precise resource ('Chromium-based browser profile'), then enumerates the supported browsers and the filter ('that has bookmarks'). It is clearly distinct from the sibling bookmark-mutation tools, though it never names an alternative explicitly.

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 only implied: an agent can infer this is a discovery/entry-point call for locating profiles before calling tools like get_bookmarks or backup. There is no explicit 'use this when...' statement, no mention of what to do if no profiles are returned, and no stated alternatives.

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