Bookmark Manager MCP

List Bookmarks

list

Retrieve all stored bookmarks from the Bookmark Manager MCP server to view and manage your categorized web links.

Instructions

List all bookmarks

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

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/index.ts:71-78 (handler)
The handler function for the 'list' tool - an async arrow function that returns all bookmarks as JSON-formatted text in the MCP content format
```
async () => {
  return {
    content: [{
      type: 'text',
      text: JSON.stringify(bookmarks, null, 2)
    }]
  }
}
```
src/index.ts:66-69 (schema)
Schema definition for the 'list' tool with title, description, and empty inputSchema (no parameters required)
```
{
  title: 'List Bookmarks',
  description: 'List all bookmarks',
  inputSchema: {}
```

src/index.ts:65-79 (registration)

Registration of the 'list' tool with the MCP server using server.registerTool() method

server.registerTool('list',
  {
    title: 'List Bookmarks',
    description: 'List all bookmarks',
    inputSchema: {}
  },
  async () => {
    return {
      content: [{
        type: 'text',
        text: JSON.stringify(bookmarks, null, 2)
      }]
    }
  }
)

src/index.ts:17-21 (schema)
TypeScript type definition for Bookmark object structure with title, url, and category fields
```
type Bookmark = {
  title: string,
  url: string,
  category: string
}
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 11, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether this is a read-only operation, how results are returned (e.g., format, pagination), or any limitations like rate constraints or authentication needs.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it immediately clear what the tool does without unnecessary elaboration.

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 simple list tool with 0 parameters and no output schema, the description is minimally adequate but lacks context about behavioral traits (e.g., read-only nature, result format). Without annotations or output schema, it should ideally mention these to be more complete for agent use.

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?

The tool has 0 parameters with 100% schema coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter semantics, and 'List all bookmarks' appropriately implies no filtering parameters are required, aligning with the schema.

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 'List all bookmarks' clearly states the verb ('List') and resource ('bookmarks'), with 'all' providing scope. However, it doesn't differentiate from the sibling 'add' tool, which would require mentioning it's for retrieval rather than creation.

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?

The description provides no guidance on when to use this tool versus the 'add' sibling. It doesn't mention prerequisites, alternatives, or exclusions, leaving the agent to infer usage from the tool name alone.

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

Deploy Server

Other Tools

addC
listB