rainkeeper

Overview Schema Source Related Servers Discussions Admin

list_raindrops

Retrieve bookmarks from a Raindrop.io collection by ID, with sorting and pagination options.

Instructions

List bookmarks in a collection. collection_id 0 = All, -1 = Unsorted. sort: -created, title, -title, domain. Maximum per_page is 50.

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

Input Schema

Name	Required	Description	Default
`page`	No
`sort`	No
`per_page`	No
`collection_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Discloses maximum per_page and allowed sort values, but omits pagination behavior, authentication requirements, and read-only nature.

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 concise sentences front-loading the purpose and key parameter details with zero waste.

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

Completeness4/5

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

Covers most parameters and constraints. Lacks pagination behavior details for the page parameter, but output schema presumably covers return structure.

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?

Schema description coverage is 0%, but description explains collection_id special values, sort options, and per_page limit. Missing explanation for the page parameter (default 0 vs. 1-based indexing).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'List bookmarks in a collection' with specific verb and resource. Provides special values for collection_id and sort options, distinguishing it from siblings like search_raindrops.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit guidance on collection_id special values and sort options. Does not explicitly mention when not to use this tool or alternatives, but the context is clear.

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