mcp-mealie

create_shopping_items_bulk

Bulk create shopping items from a JSON array. Each item requires a shopping list ID and can include optional note and quantity.

Instructions

Bulk-create shopping items from a JSON array.

items_json is a JSON array of item objects. Each item must include shoppingListId (UUID); note and quantity are typical optional fields.

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": {
      "items_json": "<items_json>"
    },
    "name": "create_shopping_items_bulk"
  }
}

Input Schema

Name	Required	Description	Default
`items_json`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Jun 19, 2026

TDQS

A4/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 burden of disclosure. It mentions bulk creation (a mutating operation) and input format, but lacks details on error handling, partial failures, idempotency, or rate limits, which are important for a bulk mutation tool.

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?

The description is two sentences long, front-loaded with the primary purpose, and no extraneous content. Every sentence adds value: purpose and parameter details.

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

Completeness3/5

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

The tool creates multiple items (moderate complexity) and has an output schema (not shown). The description adequately explains the input format but omits information about output, validation, error handling, or limits. It is minimally complete given the missing annotations.

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

Parameters5/5

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

The input schema provides no description for the 'items_json' parameter (0% coverage). The description fully compensates by specifying it is a JSON array of item objects, with required field 'shoppingListId' and optional fields 'note' and 'quantity'. This adds essential meaning beyond the schema.

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 starts with 'Bulk-create shopping items from a JSON array,' which clearly states the action (bulk-create), resource (shopping items), and input format (JSON array). This distinguishes it from the sibling tool 'create_shopping_item' for single item creation.

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 explains the input structure and notes that 'note' and 'quantity' are optional, giving context for when to use this tool for batch operations. However, it does not explicitly state when not to use it or compare with alternatives like 'create_shopping_item'.

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

Deploy Server