Unofficial Monsieur Cuisine MCP

Overview Schema Source Related Servers Discussions Admin

Remove Favorite Recipe

remove_favorite_recipe

Removes a recipe from the logged-in user's favorites by its translation ID, so you can clean up bookmarked recipes after finding the correct ID in the favorites list.

Instructions

Remove a recipe from the logged-in user's favorites (bookmarks).

Requires a saved login session: run uv run monsieur-cuisine-mcp-login once beforehand to log in manually in a browser window. If no session is saved, this tool raises an error telling the user to do that.

IMPORTANT: translation_id is the bookmark/recipe translationId field from a list_favorite_recipes result - NOT the numeric recipe id used by get_recipe/search_recipes. Always call list_favorite_recipes first to look up the correct translationId for the recipe to remove.

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": {
      "translation_id": "<translation_id>"
    },
    "name": "remove_favorite_recipe"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Locale for the response message, e.g. "pl-PL", "en-US".	en-US
`translation_id`	Yes	The `translationId` of the favorite to remove, from a list_favorite_recipes result.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the saved-login requirement, the exact login command, and the error behavior when no session exists. It does not explicitly state idempotency or reversibility, but it makes clear this is a bookmark removal rather than recipe deletion.

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?

The purpose is front-loaded, then the login prerequisite, then the critical translation_id warning. The description is somewhat long, but each paragraph addresses a real invocation risk; the schema overlap in the final warning is justified by its importance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists, the description need not explain return values. It covers the key missing context for a mutation tool with no annotations: authentication flow, error behavior, and the non-obvious identifier source.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds critical meaning beyond the schema: translation_id must come from list_favorite_recipes and is NOT the numeric recipe id used by get_recipe/search_recipes. This directly prevents a likely invocation error.

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 states a specific verb and resource: removing a recipe from the logged-in user's favorites/bookmarks. It clearly distinguishes itself from siblings like add_favorite_recipe and list_favorite_recipes, so an agent can identify the operation without opening the schema.

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

Usage Guidelines5/5

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

It explicitly tells the agent to call list_favorite_recipes first to obtain the correct translation_id, and it names the login prerequisite before use. It also warns against using the numeric recipe id from get_recipe/search_recipes, which is exactly the alternative-parameter confusion an agent could otherwise fall into.

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