Skip to main content
Glama
Sign In
rainkeeper

rainkeeper

by simonives
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bulk_move_raindrops

Move multiple bookmarks from a source collection to a target collection using bookmark IDs and collection IDs. IDs from other collections are skipped.

Instructions

Move multiple bookmarks to a target collection. ids must be non-empty and all from source_collection_id — ids from other collections are silently skipped by the API.

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": {
      "ids": "<ids>",
      "source_collection_id": "<source_collection_id>",
      "target_collection_id": "<target_collection_id>"
    },
    "name": "bulk_move_raindrops"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
source_collection_idYes
target_collection_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description discloses the silent skipping behavior, which is helpful. However, it omits other behavioral details like success response, partial failure handling, or atomicity.

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 that front-load the core purpose and immediately follow with critical constraint. No unnecessary words.

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?

With an output schema likely covering return values, the description is reasonably complete for a bulk operation. It could mention prerequisites or failure scenarios, but the constraint and behavioral note add sufficient context.

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?

Despite 0% schema description coverage, the description adds meaning beyond the schema by imposing constraints ('non-empty', 'all from source_collection_id') and explaining the silent skip behavior for ids from other collections.

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?

The description clearly states the action ('Move multiple bookmarks') and resource ('to a target collection'). It distinguishes from sibling tools like 'move_raindrop' (single) and 'bulk_delete_raindrops' (different action).

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 provides important constraints ('ids must be non-empty and all from source_collection_id') and a behavioral caveat ('ids from other collections are silently skipped'). However, it does not explicitly compare to alternative tools like 'move_raindrop' for single moves.

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