Skip to main content
Glama
ni-c

mealie-mcp

by ni-c
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Delete cookbook

delete_cookbook
DestructiveIdempotent

Delete a saved cookbook (a filter for recipes) without affecting the recipes themselves. Requires a confirmation token from a prior call to proceed.

Instructions

Deletes a cookbook. The recipes it matched are not touched — a cookbook is only a saved filter. Requires confirmation: call once to receive a token, then again with that token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cookbook_idYesCookbook UUID, from list_cookbooks
confirm_tokenNoConfirmation token from a previous call of this tool with the same arguments. Omit on the first call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
truncatedNoPresent only when entries were dropped to fit the budget.
deleted_cookbook_idYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / maxLength
      Added value: +512
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "deleted_cookbook_id": {
+      "type": "string"
+    },
+    "truncated": {
+      "additionalProperties": true,
+      "description": "Present only when entries were dropped to fit the budget.",
+      "properties": {
+        "follow_up": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason",
+        "follow_up"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "deleted_cookbook_id"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses the destructive action, the non-destructive effect on recipes, and the two-step confirmation process. This goes beyond the annotations by explaining the exact sequence and side effects.

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?

The description is brief, well-structured, and contains no redundant information. Every sentence contributes essential details about the operation, the confirmation requirement, and the non-destructive nature for recipes.

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 the moderate complexity of a two-step destructive operation, the description provides all necessary context: what is deleted, what is not affected, and the exact confirmation process. No critical information is missing.

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

Parameters4/5

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

The schema already provides full parameter descriptions with 100% coverage. The tool description adds meaningful context about the confirmation token flow, which clarifies the role of confirm_token beyond the schema's basic description.

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 clearly states the tool deletes a cookbook, specifies that recipes are not affected, and differentiates cookbooks from recipes by calling them saved filters. This distinguishes it from sibling tools like delete_recipe.

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 explains the required confirmation workflow: call once to get a token, then call again with that token. It also clarifies that recipes are not touched, which helps the agent decide when this tool is appropriate versus other deletion tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ni-c/mealie-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server