Skip to main content
Glama
counterbeing

mealie-mcp-ts

by counterbeing

update_recipe

Update an existing recipe by slug, changing only the fields you specify. Use natural language ingredient text like '2 cups flour' for automatic parsing into quantity, unit, and food.

Instructions

Update an existing recipe by slug. Only provided fields will be updated. For ingredients, prefer passing originalText (e.g. "2 cups flour") over structured {quantity, unit, food} — the server parses originalText and auto-resolves unit+food. Structured form also works and is auto-normalized, but originalText is simpler.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the recipe
slugYesRecipe slug to update
cookTimeNoCook time (e.g., "20 minutes")
prepTimeNoPrep time (e.g., "10 minutes")
totalTimeNoTotal time (e.g., "30 minutes")
descriptionNoDescription of the recipe
recipeYieldNoYield of the recipe (e.g., "4 servings")
recipeIngredientNoList of ingredients. Each ingredient can either have originalText (to be parsed automatically) or structured fields (quantity, unit, food, note). To group ingredients into sections like "For the sauce", insert standalone {"title": "For the sauce"} entries between groups — Mealie will render them as section headers.
recipeInstructionsNoList of instructions
Behavior4/5

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

With no annotations, the description carries full burden. It discloses partial-update semantics and server-side parsing/normalization of ingredients, which are key behavioral traits beyond the schema. However, it omits error handling, auth, or response details.

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, front-loaded with the core operation, and no filler. The ingredient guidance earns its place.

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

Completeness4/5

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

The schema is rich and self-explanatory for parameters. The description covers the essential update behavior and ingredient best practice. The absence of return-value explanation is a minor gap given no output schema.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the tradeoff between originalText and structured ingredient input, and by clarifying partial updates affect all parameters.

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 "Update an existing recipe by slug," which is a specific verb+resource+identifier. It clearly distinguishes this from create_recipe, delete_recipe, and get_recipe.

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

Usage Guidelines4/5

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

The description clearly implies use for modifying existing recipes with "Update an existing recipe by slug" and explains the partial-update behavior ("Only provided fields will be updated"). It also gives parameter-level guidance (prefer originalText over structured), but doesn't explicitly name alternative tools like create_recipe for new recipes.

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/counterbeing/mealie-mcp-ts'

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