Better Mealie MCP

Overview Schema Source Related Servers Discussions Admin

Patch Recipes By Slug

patch_recipes_by_slug

Update an existing recipe by its slug, applying partial changes to fields like ingredients, instructions, tags, or nutrition without replacing the whole recipe.

Instructions

Updates a recipe by existing slug and data.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No
`name`	No
`slug`	No
`tags`	No
`image`	No
`notes`	No
`tools`	No
`assets`	No
`extras`	No
`orgURL`	No
`rating`	No
`userId`	No
`groupId`	No
`comments`	No
`cookTime`	No
`lastMade`	No
`prepTime`	No
`settings`	No
`createdAt`	No
`dateAdded`	No
`nutrition`	No
`totalTime`	No
`update_at`	No
`slug__path`	Yes	(Path parameter)
`dateUpdated`	No
`description`	No
`householdId`	No
`performTime`	No
`recipeYield`	No
`recipeCategory`	No
`recipeServings`	No
`accept-language`	No
`recipeIngredient`	No
`recipeInstructions`	No
`recipeYieldQuantity`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.28.0Sep 27, 2026

changedInput schema / $defs / RecipeCommentOut-Input / required

Previous value: -[
-  "recipeId",
-  "text",
-  "id",
-  "createdAt",
-  "update_at",
-  "userId",
-  "user"
-]New value: +[
+  "id",
+  "recipeId",
+  "text",
+  "createdAt",
+  "update_at",
+  "userId",
+  "user"
+]

Changed10 schema fields changedv3.26.0Sep 15, 2026

addedInput schema / $defs / CreateIngredientFood / properties / substitutions

Added value: +{
+  "items": {
+    "$ref": "#/$defs/CreateIngredientFoodSubstitution"
+  },
+  "type": "array"
+}

addedInput schema / $defs / CreateIngredientFoodSubstitution

Added value: +{
+  "properties": {
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFoodId": {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / $defs / IngredientFood-Input / properties / substitutions

Added value: +{
+  "items": {
+    "$ref": "#/$defs/IngredientFoodSubstitution"
+  },
+  "type": "array"
+}

addedInput schema / $defs / IngredientFoodSubstitution

Added value: +{
+  "properties": {
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFood": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/IngredientFoodSummary"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFoodId": {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / $defs / IngredientFoodSummary

Added value: +{
+  "description": "A trimmed projection of a food, with nothing on it that can recurse.\n\nSubstitutions reference this rather than the full IngredientFood, which would make\nPydantic walk food -> substitutions -> food forever and generate an equally circular\nTypeScript type.",
+  "properties": {
+    "id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "pluralName": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name"
+  ],
+  "type": "object"
+}

addedInput schema / $defs / NoteReference

Added value: +{
+  "properties": {
+    "referenceId": {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / $defs / RecipeIngredient-Input / properties / substitutions

Added value: +{
+  "items": {
+    "$ref": "#/$defs/RecipeIngredientSubstitution"
+  },
+  "type": "array"
+}

addedInput schema / $defs / RecipeIngredientSubstitution

Added value: +{
+  "properties": {
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFood": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/IngredientFoodSummary"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFoodId": {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / $defs / RecipeNote / properties / referenceId
```
Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
```

addedInput schema / $defs / RecipeStep / properties / noteReferences

Added value: +{
+  "items": {
+    "$ref": "#/$defs/NoteReference"
+  },
+  "type": "array"
+}

Changed3 schema fields changedv3.25.1Sep 8, 2026
- addedInput schema / $defs / RecipeCategory / properties / recipeCount
```
Added value: +{
+  "type": "integer"
+}
```
- addedInput schema / $defs / RecipeTag / properties / recipeCount
```
Added value: +{
+  "type": "integer"
+}
```
- addedInput schema / $defs / RecipeTool / properties / recipeCount
```
Added value: +{
+  "type": "integer"
+}
```
First observedv3.20.1Jul 10, 2026

TDQS

C2.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says the tool updates a recipe but omits critical PATCH semantics: whether omitted fields are preserved, what permissions are required, whether the change is reversible, and what the response contains. For a mutation tool of this complexity, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no padding, which is structurally clean. However, it is under-specified for a tool with 35 parameters, so its brevity reflects omission rather than efficient communication.

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

Completeness1/5

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

Given a 35-parameter mutation endpoint, no annotations, and no output schema, the description is far too thin. It should explain partial-update behavior, authorization needs, and how this differs from update_recipes_by_slug, but it provides none of that.

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

Parameters2/5

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

Schema description coverage is only 3% across 35 parameters, so the description must compensate. It mentions 'slug' and 'data' generically, which loosely maps to the required path parameter and request body, but adds no meaning for any of the remaining 34 fields (tags, nutrition, settings, etc.).

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

Purpose3/5

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

The description states a specific verb (Updates) and resource (a recipe) identified by slug, so the basic purpose is clear. However, it does not distinguish this PATCH operation from nearby siblings like update_recipes_by_slug, patch_recipes, or patch_recipes_by_slug_last_made, and the phrase 'and data' is tautological.

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. The description does not name alternatives such as update_recipes_by_slug (likely full replacement) or patch_recipes (likely by id), leaving the agent to guess which sibling applies.

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

Deploy Server

Patch Recipes By Slug

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools