Skip to main content
Glama
ni-c

mealie-mcp

by ni-c

Update recipe

update_recipe

Update specific fields of a recipe in Mealie without altering others. Change name, ingredients, instructions, or clear lists by passing empty arrays.

Instructions

Changes individual fields of a recipe. Only the fields given are touched; everything else keeps its value. Passing an empty array for ingredients, instructions, tags or categories clears that list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
tagsNoTag names. They replace the existing tags; unknown names are created.
notesNo
recipeYesRecipe slug (e.g. "quark-bowl") or recipe UUID — both are returned by search_recipes
servingsNo
cook_timeNo
prep_timeNo
categoriesNoCategory names. They replace the existing categories.
source_urlNoOriginal source of the recipe, stored as orgURL
total_timeNo
descriptionNo
ingredientsNoIngredient lines as free text, e.g. "500 g quark". They replace the existing list. Use parse_ingredients first if structured food and unit references are wanted.
instructionsNoPreparation steps, in order. They replace the existing list.
recipe_yieldNo
Behavior4/5

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

The annotations already declare destructiveHint=false and readOnlyHint=false. The description adds value by explaining the partial-update behavior ('Only the fields given are touched') and the clearing effect of empty arrays. However, it does not disclose potential side effects, auth requirements, or validation failure modes.

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?

Two sentences precisely deliver the essential information with no wasted words. The purpose is front-loaded and the behavioral detail is efficiently appended.

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

Completeness2/5

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

Given 14 parameters, low schema coverage, no output schema, and numerous sibling tools for specific edits, the description is insufficient. It does not mention what is returned, how to handle validation errors, or guide the agent toward more appropriate tools for rating, commenting, or other specific modifications.

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 low at 43%. The description adds general parameter semantics about partial updates and list clearing, but does not provide detailed meaning for the 8 parameters lacking schema descriptions. It compensates somewhat but not fully.

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 uses the specific verb 'changes' and identifies the resource 'fields of a recipe', clearly distinguishing from sibling tools like create_recipe or delete_recipe. It also adds the nuance that only given fields are touched, which further clarifies scope.

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

Usage Guidelines3/5

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

The description implies that this tool should be used when modifying existing recipe fields, but it does not explicitly state when to use it versus more specific sibling tools like set_recipe_rating or add_recipe_comment. No alternative tools or when-not-to-use conditions are given.

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