MCP: Collection emoji/icon not settable via API

[axelquack]

Summary: The REST PUT /collection/{id} API accepts a color field (hex string) and stores it correctly. However, an icon field with an emoji value is silently ignored — no error, not stored. The Raindrop UI allows setting emoji icons on collections, but there is no API equivalent.

• Expected: An icon or emoji field accepted by PUT /collection/{id} to set the collection icon programmatically.
• Actual: Field is silently ignored. Only title, description, parent_id, and color are writable via API.
• Note: color (hex string) does work correctly via REST — this request is specifically for emoji/icon support.
• Related: https://github.com/axelquack/raindrop-mcp-scripts

[exentrich]

To see what's available in MCP, you can list all tools and their parameters with this call:

POST /rest/v2/ai/mcp HTTP/1.1
Content-Type: application/json
{"jsonrpc":"2.0","id":"1","method":"tools/list"}

As for PUT /collection/{id} — the icon field only supports a URL, not an emoji. It's possible I'm overlooking something, though. Could you clarify what's missing from your perspective?

[axelquack]

Thanks for the pointer to tools/list - helpful for inspecting the schema.

To clarify what I am referring to: not URL-based image icons, but the emoji characters that appear next to collection names in the Raindrop sidebar - the ones you set in the UI via right-click → Edit → clicking the icon area in the modal (e.g. 🎮, 💰, 🤖).

These don't appear to be exposed in the API at all, either for reading or writing. The MCP find_collections response only returns collection_id, title, created, parent_id, and bookmark counts - no icon or emoji field. And passing an emoji character to the icon field in PUT /collection/{id} is silently ignored.

Is this emoji icon stored in an internal field that isn't exposed via the public API? If so, even read-only access to it would be useful - that way automation scripts could at least know which emoji is set, even if writing it isn't supported yet.

[exentrich]

Maybe it's better suited for you to use API instead of MCP? It has complete functionality.
We consciously reduced functionality for MCP to bare minimum so LLMs not struggle to use them, more tokens, more chance for hallucination.
Also I'm still not sure about emojis you talking about. Raindrop do not support setting emoji as an icon, you can select only a PNG from predefined set or provide your own with URL.