Skip to main content
Glama
ni-c

mealie-mcp

by ni-c
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Delete a tag, category or tool

delete_organizer
DestructiveIdempotent

Delete a tag, category, or tool from Mealie. Recipes remain but lose this assignment. Requires a confirmation token: call once to get it, then confirm with the token.

Instructions

Deletes a tag, category or tool. The recipes themselves are kept, but they lose the assignment. Requires confirmation: call once to receive a token, then again with that token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUUID from list_organizers
kindYesWhich organizer: "tag" (free-form labels), "category" (the primary classification, one recipe usually has few) or "tool" (equipment a recipe needs)
confirm_tokenNoConfirmation token from a previous call of this tool with the same arguments. Omit on the first call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
deletedYes
truncatedNoPresent only when entries were dropped to fit the budget.
deleted_idYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / maxLength
      Added value: +512
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "deleted": {
+      "type": "string"
+    },
+    "deleted_id": {
+      "type": "string"
+    },
+    "truncated": {
+      "additionalProperties": true,
+      "description": "Present only when entries were dropped to fit the budget.",
+      "properties": {
+        "follow_up": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason",
+        "follow_up"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "deleted",
+    "deleted_id"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses the destructive nature (deletes), the confirmation requirement, and the effect on recipes (they lose the assignment). It does not mention irreversibility or cascading effects, but annotations already cover destructiveHint and idempotentHint.

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, no fluff, essential information only. The confirmation flow is clearly stated in a compact manner.

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?

Given the output schema exists and the description is sufficient for typical usage, it is complete. Slight gap: no mention of error cases (e.g., invalid token) or whether the operation is reversible, but these are not critical for basic invocation.

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?

The description clarifies that confirm_token comes from a previous call and explains the meaning of 'kind' with examples. Schema already covers types and constraints, so the description adds meaningful context without redundancy.

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?

Description clearly states the verb 'deletes' and the specific resource types (tag, category, tool). It also notes the effect on recipes, distinguishing it from create/update counterparts.

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 two-step confirmation process is described, but no explicit guidance on when to use this tool versus alternatives like update_organizer or delete_recipe is given. The context from sibling tools is implicit.

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