Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

Create Recipes Bulk Actions Categorize

create_recipes_bulk_actions_categorize

Assign categories to many recipes at once, helping you organize large recipe collections by category without editing each recipe individually.

Instructions

Bulk Categorize Recipes

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recipes": "<recipes>",
      "categories": "<categories>"
    },
    "name": "create_recipes_bulk_actions_categorize"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipesYes
categoriesYes
accept-languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv3.31.0
    • addedInput schema / properties / categories / items / properties / id / anyOf
      Added value: +[
      +  {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / categories / items / properties / id / format
      Removed value: -"uuid"
    • removedInput schema / properties / categories / items / properties / id / type
      Removed value: -"string"
    • addedInput schema / properties / categories / items / properties / recipeCount
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / categories / items / properties / slug / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / categories / items / properties / slug / type
      Removed value: -"string"
    • changedInput schema / properties / categories / items / required
      Previous value: -[
      -  "name",
      -  "id",
      -  "slug"
      -]New value: +[
      +  "name"
      +]
  2. First observedv3.20.1

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. For a mutation tool it fails to say whether categorization replaces or appends to existing categories, whether it requires specific permissions, or what happens to recipes not matched.

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?

The text is short, but brevity here is under-specification rather than conciseness; there is no structure, no front-loaded scope statement, and no sentence that earns its place by informing the caller.

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?

A bulk mutation with a nested parameter object, no annotations, and no output schema needs the description to explain semantics, side effects, and response shape. The four-word definition covers none of this, making it inadequate for the tool's complexity.

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?

Schema description coverage is 0% across three parameters, including a nested categories array with id/name/slug/groupId fields. The description adds no meaning for recipes, categories, or accept-language, leaving the agent to infer the identifier vs. name matching behavior entirely on its own.

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?

"Bulk Categorize Recipes" only restates the tool name and title, adding no detail beyond the tokens already present. It does convey a verb (categorize) and resource (recipes), but gives no scope, no indication of what the operation does to existing categories, and nothing distinguishing it from siblings like create_recipes_bulk_actions_tag or create_recipes_bulk_actions_settings.

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 guidance, no mention of alternatives among the many bulk-actions siblings, and no prerequisites or exclusions. The word "Bulk" weakly implies a multi-recipe operation, which is the only usage signal present.

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

Deploy Server

Other Tools