Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Get bookmarks

get_bookmarks

List bookmarks and folders for a browser profile with IDs and folder paths. Filter by folder ID to inspect a single folder, or return folders only for a quick structure overview.

Instructions

Lists bookmarks and folders of a profile with their ids and folder path. Use folder_id to look inside one folder, and folders_only for a quick overview of the structure.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
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_idNoOnly list items inside this folder (recursively).
folders_onlyNo

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, the description must carry the behavioral burden. It correctly signals a read operation and discloses the returned fields (ids, folder path), which matters since there is no output schema. It omits pagination behavior despite limit/offset parameters defaulting to 300/0 with a 2000 cap, and says nothing about permissions or recursion semantics.

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?

Two short sentences, zero filler, with the core behavior front-loaded and parameter hints following. Nothing could be removed without losing information.

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 five-parameter read tool with no output schema and no annotations, the definition covers what is returned at a high level but leaves paging behavior and the profile-selection prerequisite (optional only when a single profile exists) unstated in prose. Adequate but with clear gaps.

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 only 40%, so the description should compensate more than it does. It adds real meaning for folders_only ("quick overview of the structure") beyond the bare boolean, and frames folder_id's purpose, but limit, offset, and the profile-string handling are left entirely to the schema's partial descriptions.

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?

"Lists bookmarks and folders of a profile with their ids and folder path" is a specific verb plus resource with the shape of the returned items named. It does not differentiate from search_bookmarks or list_profiles, but the purpose itself is unambiguous.

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?

The description gives usage guidance for two of the five parameters (folder_id for scoping into a folder, folders_only for a structure overview), which implies when to reach for each. It never says when to use this tool versus search_bookmarks (filtering) or list_profiles (obtaining a profile id), so cross-tool routing is left to inference.

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