Bookmark Manager MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| addC | Add a new bookmark |
| listB | List all bookmarks |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| bookmarks://all | All bookmarks |
| bookmarks://mcp | MCP bookmarks |
| bookmarks://general | General bookmarks |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'add' is for creating new bookmarks, while 'list' is for retrieving existing ones. There is no overlap or ambiguity between these operations, making it easy for an agent to select the correct tool based on the task.
Both tools use simple, imperative verb names ('add' and 'list') that follow a consistent pattern. This naming style is clear and predictable, with no deviations or mixed conventions, ensuring readability and ease of use.
With only two tools, the server feels under-scoped for a bookmark manager, as it lacks essential operations like update, delete, or search. While the count is minimal, it does not provide complete coverage for basic CRUD functionality, making it borderline too few for the domain.
The toolset is severely incomplete for a bookmark manager, missing key operations such as update, delete, and search. This creates significant gaps that will likely cause agent failures when trying to manage bookmarks fully, as users cannot modify or remove entries.