Cookidoo MCP Server

Overview Schema Source Related Servers Discussions Admin

Add To Collection

add_to_collection

Add Cookidoo catalogue recipes to a user's custom collection by collection ID and up to 50 recipe IDs. Use it to organize saved recipes into collections.

Instructions

Add Cookidoo catalogue recipes to one of the user's custom collections.

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>",
      "recipe_ids": "<recipe_ids>"
    },
    "name": "add_to_collection"
  }
}

Input Schema

Name	Required	Description	Default
`recipe_ids`	Yes	Cookidoo catalogue recipe IDs (e.g. "r59322")
`collection_id`	Yes	ID from list_collections (kind="custom")

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the useful constraint that only catalogue recipes can be added (not the user's own custom recipes), but says nothing about duplicate handling, whether existing collection contents are preserved, or the 50-item cap.

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?

A single front-loaded sentence with zero filler, correctly sized for a two-parameter mutation. It is efficient but so terse that the resource scope has to be inferred from the phrase 'catalogue recipes'.

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?

An output schema and full parameter coverage mean the description does not need to explain return values or arguments. However, for a mutation whose nearest sibling is copy_recipe_to_custom, the missing distinction and the silence on duplicates/append semantics leave a real gap.

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 description coverage is 100%; both collection_id and recipe_ids already carry descriptions and an ID format example. The description adds no meaning beyond the schema, 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?

States a specific verb (Add), a specific resource (Cookidoo catalogue recipes) and a specific destination (one of the user's custom collections). This implicitly separates it from add_to_meal_plan and add_recipes_to_shopping_list, but no sibling is named explicitly, so it falls short of 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of prerequisites such as needing a collection created via create_collection. The most important ambiguity, when to use this versus copy_recipe_to_custom, is left entirely to inference.

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