rainkeeper

Overview Schema Source Related Servers Discussions Admin

create_raindrop

Save a new bookmark to Raindrop.io by providing a link and optionally specifying note, tags, title, importance, and collection.

Instructions

Save a new bookmark. collection_id -1 = Unsorted. Tags is a list of strings. Pass title='' to explicitly clear the auto-detected title.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "link": "<link>"
    },
    "name": "create_raindrop"
  }
}

Input Schema

Name	Required	Description	Default
`link`	Yes
`note`	No
`tags`	No
`title`	No
`important`	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.1/5.0

Behavior4/5

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

With no annotations, the description discloses key behaviors: special value for collection_id (-1 for Unsorted), tags format, and clearing auto-detected title. This adds value beyond the schema, though it doesn't cover all traits like authentication or rate limits.

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?

Three sentences, each adding specific value: purpose, parameter hints, and a practical tip. No wasted words; information is front-loaded.

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 6 parameters and no schema descriptions or annotations, the description partially explains parameters (3 out of 6) and behavior. Output schema exists but isn't referenced. Missing details on note and important could lead to incomplete understanding.

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 coverage is 0%, so description must compensate. It explains collection_id, tags, and title (3 of 6 parameters), but omits details for link, note, and important. Provides useful context but not comprehensive.

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?

Description clearly states 'Save a new bookmark' – a specific verb and resource. It distinguishes from sibling tools like update_raindrop, delete_raindrop, and bulk operations, making its purpose unambiguous.

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?

The description implies usage for creating bookmarks, but does not explicitly state when not to use it (e.g., for updates) or compare to alternatives. However, given the context of a create tool and sibling names, the guidance is clear enough.

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