Cookidoo MCP Server

by herp75

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Unfollow Collection

unfollow_collection

DestructiveIdempotent

Stop following a Cookidoo collection to remove it from your followed collections; it can be followed again later.

Instructions

Stop following a Cookidoo collection. It disappears from the user's followed collections (it can be followed again later).

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": {
      "collection_id": "<collection_id>"
    },
    "name": "unfollow_collection"
  }
}

Input Schema

Name	Required	Description	Default
`collection_id`	Yes	ID from list_collections (kind="managed")

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description contributes the genuinely useful fact that the relationship is reversible — the collection vanishes from the followed list yet can be re-followed. That reframes what 'destructive' means here and is not derivable from the annotations, though nothing is said about auth requirements or side effects beyond the user's follow list.

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 short sentences, front-loaded with the action, with the parenthetical carrying the one non-obvious behavioral nuance. Nothing is redundant with the annotations or the schema.

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?

For a single-parameter, idempotent unfollow operation with an output schema handling the return value, the description covers what an agent needs to act correctly. Only minor gaps remain, such as whether the action requires an active Cookidoo connection or how a non-followed collection is handled.

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?

Only one parameter and the schema already documents it at 100% coverage, including the pointer to list_collections (kind="managed"). The description adds no further meaning about the identifier beyond what the schema provides, so the baseline of 3 applies.

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

Purpose4/5

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

The description gives a specific verb+resource ('Stop following a Cookidoo collection'), and the parenthetical that it 'can be followed again later' implicitly separates it from the sibling delete_collection, which is the most plausible confusion. It stops just short of naming the inverse/alternative tools outright, so a 4 rather than a 5.

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 clearly implied — call this when the user wants to unfollow rather than delete — but there is no explicit when-to-use / when-not-to-use statement and no named alternatives (follow_collection, delete_collection) despite them existing in the sibling set.

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