Skip to main content
Glama

search-bookmarks

Search and filter your Raindrop.io bookmarks by query, tags, or collection. Sort results and paginate for efficient access to saved content.

Instructions

Search through your Raindrop.io bookmarks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionNoCollection ID to search in (optional, 0 for all collections)
pageNoPage number (0-based, optional)
perpageNoItems per page (1-50, optional)
queryYesSearch query
sortNoSort order (optional). Prefix with - for descending order.
tagsNoFilter by tags (optional)
wordNoWhether to match exact words only (optional)

Implementation Reference

  • Executes the 'search-bookmarks' tool: validates input, constructs search parameters, calls Raindrop API, formats and returns results.
          if (name === "search-bookmarks") {
            const { query, tags, page, perpage, sort, collection, word } =
              SearchBookmarksSchema.parse(args);
    
            const searchParams = new URLSearchParams({
              search: query,
              ...(tags && { tags: tags.join(",") }),
              ...(page !== undefined && { page: page.toString() }),
              ...(perpage !== undefined && { perpage: perpage.toString() }),
              ...(sort && { sort }),
              ...(word !== undefined && { word: word.toString() }),
            });
    
            const collectionId = collection ?? 0;
            const results = await api.searchBookmarks(collectionId, searchParams);
    
            const formattedResults = results.items
              .map(
                (item) => `
    Title: ${item.title}
    URL: ${item.link}
    Tags: ${item.tags?.length ? item.tags.join(", ") : "No tags"}
    Created: ${new Date(item.created).toLocaleString()}
    Last Updated: ${new Date(item.lastUpdate).toLocaleString()}
    ---`,
              )
              .join("\n");
    
            return {
              content: [
                {
                  type: "text",
                  text:
                    results.items.length > 0
                      ? `Found ${results.count} total bookmarks (showing ${
                          results.items.length
                        } on page ${page ?? 0 + 1}):\n${formattedResults}`
                      : "No bookmarks found matching your search.",
                },
              ],
            };
          }
  • MCP tool definition for 'search-bookmarks' including input schema for validation.
    {
      name: "search-bookmarks",
      description: "Search through your Raindrop.io bookmarks",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search query",
          },
          tags: {
            type: "array",
            items: { type: "string" },
            description: "Filter by tags (optional)",
          },
          page: {
            type: "number",
            description: "Page number (0-based, optional)",
          },
          perpage: {
            type: "number",
            description: "Items per page (1-50, optional)",
          },
          sort: {
            type: "string",
            enum: [
              "-created",
              "created",
              "-last_update",
              "last_update",
              "-title",
              "title",
              "-domain",
              "domain",
            ],
            description:
              "Sort order (optional). Prefix with - for descending order.",
          },
          collection: {
            type: "number",
            description:
              "Collection ID to search in (optional, 0 for all collections)",
          },
          word: {
            type: "boolean",
            description: "Whether to match exact words only (optional)",
          },
        },
        required: ["query"],
      },
    },
  • src/index.ts:29-31 (registration)
    Registers the list of available tools, including 'search-bookmarks', via ListToolsRequest handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • Helper method in RaindropAPI that performs the API search request to Raindrop.io.
      async searchBookmarks(
        collectionId: number,
        searchParams: URLSearchParams,
      ): Promise<SearchResponse> {
        return this.makeRequest<SearchResponse>(
          `/raindrops/${collectionId}?${searchParams.toString()}`,
        );
      }
    
      async listCollections(): Promise<CollectionsResponse> {
        return this.makeRequest<CollectionsResponse>("/collections");
      }
    }
  • Zod schema for validating 'search-bookmarks' tool arguments.
    export const SearchBookmarksSchema = z.object({
      query: z.string(),
      tags: z.array(z.string()).optional(),
      page: z.number().min(0).optional(),
      perpage: z.number().min(1).max(50).optional(),
      sort: z
        .enum([
          "-created",
          "created",
          "-last_update",
          "last_update",
          "-title",
          "title",
          "-domain",
          "domain",
        ])
        .optional(),
      collection: z.number().optional(),
      word: z.boolean().optional(),
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic function. It doesn't mention whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior beyond parameters, or what format results return. For a search tool with 7 parameters, this is insufficient behavioral context.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a search tool and front-loads the essential information without unnecessary elaboration.

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

Completeness2/5

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

For a search tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what kind of results to expect, how pagination works beyond the parameters, or any behavioral constraints. The agent would need to rely heavily on trial-and-error or external knowledge to use this tool effectively.

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 description coverage is 100%, so all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond what's already in the schema descriptions (like explaining what 'collection ID 0' means or how search queries work). This meets the baseline for high schema coverage.

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 action ('Search through') and resource ('your Raindrop.io bookmarks'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'list-collections', but the verb 'search' implies filtering capabilities beyond basic listing.

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?

No guidance is provided about when to use this tool versus alternatives like 'list-collections' or 'create-bookmark'. The description doesn't mention prerequisites, appropriate contexts, 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.

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