rainkeeper

Overview Schema Source Related Servers Discussions Admin

bulk_tag_raindrops

Apply tags to multiple bookmarks in a collection, merging with existing tags.

Instructions

Apply tags to multiple bookmarks. Merges with existing tags. WARNING: passing tags=[] will remove all tags from the targeted bookmarks.

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>",
      "collection_id": "<collection_id>",
      "tags": "<tags>"
    },
    "name": "bulk_tag_raindrops"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes
`tags`	Yes
`collection_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Despite no annotations, the description adds key behavioral info: merges with existing tags and warns that passing tags=[] removes all tags. This mitigates misinterpretation. However, it could mention if the operation is idempotent or whether it returns the updated bookmarks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise: two sentences and a warning. Front-loaded with purpose. The warning is appropriately prominent. Could be slightly tighter, but overall efficient.

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 has an output schema and three required params, the description covers the core behavior but omits return value details and param semantics. Sibling tools are numerous, but the description suffices for basic usage. More context around expected output would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, and the description adds minimal parameter context beyond the param names. The warning about tags=[] partially clarifies that parameter's effect, but ids and collection_id are not explained. For a schema with three required fields, more parameter-level detail would be beneficial.

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 the action 'Apply tags' to the resource 'multiple bookmarks' and specifies behavioral nuance 'Merges with existing tags'. This distinguishes it from siblings like bulk_delete_raindrops and warns against a dangerous use case.

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

Usage Guidelines3/5

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

Usage is implied (apply tags to multiple bookmarks), but no explicit guidance on when to use this tool versus others like bulk_mark_important or search_raindrops. No alternative recommendations or prerequisites are mentioned.

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