Better Mealie MCP

Overview Schema Source Related Servers Discussions Admin

Create Households Shopping Items

create_households_shopping_items

Add a shopping item to a Mealie household shopping list with food, unit, quantity, notes, and optional recipe references.

Instructions

Create One

Input Schema

Name	Required	Description	Default
`id`	No
`food`	No
`note`	No
`unit`	No
`extras`	No
`foodId`	No
`unitId`	No
`checked`	No
`display`	No
`labelId`	No
`position`	No
`quantity`	No
`shoppingListId`	Yes
`accept-language`	No
`recipeReferences`	No
`referencedRecipe`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.30.0Nov 4, 2026

addedInput schema / $defs / RecipeStep / properties / durationSeconds

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2147483647,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed5 schema fields changedv3.29.0Oct 22, 2026

addedInput schema / $defs / IngredientFood-Input / properties / recipeCount
```
Added value: +{
+  "type": "integer"
+}
```

removedInput schema / $defs / Recipe-Input / properties / lastMade

Removed value: -{
-  "anyOf": [
-    {
-      "format": "date-time",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedInput schema / $defs / Recipe-Input / properties / performTimeSeconds

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2147483647,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / $defs / Recipe-Input / properties / prepTimeSeconds

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2147483647,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / $defs / Recipe-Input / properties / totalTimeSeconds

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2147483647,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

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

D1.5/5.0

Behavior1/5

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

Annotations are absent, so the description carries the full burden, yet it discloses nothing about mutation semantics, required permissions, side effects on the parent shopping list, or what the creation returns.

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

Conciseness2/5

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

Two words are technically concise, but this is under-specification rather than efficiency; there is no useful content to be front-loaded.

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?

An output schema exists so return values need not be explained, but for a 16-parameter write tool with no annotations, a two-word description leaves an agent unable to construct a correct call.

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

Parameters1/5

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

With 16 parameters and 0% schema description coverage, the description needed to explain fields like food/foodId vs unit/unitId alternatives, quantity, position, checked, and shoppingListId, but it provides no parameter information at all.

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

Purpose2/5

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

"Create One" restates the tool name rather than describing what is created; the word "One" hints at a single shopping-list item versus the bulk sibling, but the description itself never names the resource or the household/shopping-list scope.

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?

No when-to-use guidance and no mention of alternatives such as create_households_shopping_items_create_bulk or the recipe-based item creation tools; only the implicit singular-vs-bulk distinction can be inferred from "One".

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

Deploy Server