Skip to main content
Glama

list-collections

Retrieve all Raindrop.io bookmark collections via the MCP server, enabling structured access to organize and manage saved resources directly through AI integrations.

Instructions

List all your Raindrop.io collections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'list-collections' tool: fetches collections using RaindropAPI, formats them into a text list with details (name, ID, count, parent, created date), and returns in MCP content format.
          if (name === "list-collections") {
            const collections = await api.listCollections();
    
            const formattedCollections = collections.items
              .map(
                (item) => `
    Name: ${item.title}
    ID: ${item._id}
    Count: ${item.count} bookmarks
    Parent: ${item.parent?._id || "None"}
    Created: ${new Date(item.created).toLocaleString()}
    ---`,
              )
              .join("\n");
    
            return {
              content: [
                {
                  type: "text",
                  text:
                    collections.items.length > 0
                      ? `Found ${collections.items.length} collections:\n${formattedCollections}`
                      : "No collections found.",
                },
              ],
            };
          }
  • Helper method in RaindropAPI class that makes an authenticated GET request to Raindrop.io's /collections endpoint to retrieve all collections.
    async listCollections(): Promise<CollectionsResponse> {
      return this.makeRequest<CollectionsResponse>("/collections");
    }
  • MCP tool schema definition for 'list-collections', specifying name, description, and empty input schema (no input parameters required). Included in the exported tools array.
    {
      name: "list-collections",
      description: "List all your Raindrop.io collections",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • TypeScript interface defining the structure of the Raindrop.io collections API response.
    export interface CollectionsResponse {
      items: Collection[];
    }
  • src/index.ts:29-31 (registration)
    Registers the tools list (including 'list-collections') for MCP's ListToolsRequest, making the tool discoverable.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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 of behavioral disclosure. It states 'List all your Raindrop.io collections,' which implies a read-only operation, but doesn't specify whether this requires authentication, how results are returned (e.g., pagination, format), or any rate limits. The description is minimal and lacks critical behavioral details for a tool with no annotation support.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no redundancy or 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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks context on authentication, return format, or error handling. For a list operation with no structured support, more completeness would be helpful, but it meets the basic threshold for such a simple tool.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 clearly states the verb ('List') and resource ('Raindrop.io collections'), making the purpose immediately understandable. It specifies 'all your' collections, which provides scope. However, it doesn't differentiate from sibling tools like 'search-bookmarks' or 'create-bookmark'—this is a list operation vs. search/create operations, but the description doesn't explicitly contrast them.

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 alternatives. It doesn't mention prerequisites, such as authentication or account setup, or compare it to sibling tools like 'search-bookmarks' for filtered queries. Without annotations or context, the agent must 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.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hiromitsusasaki/raindrop-io-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server