Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

Create Recipes Create Html Or Json

create_recipes_create_html_or_json

Parses raw HTML or schema.org Recipe JSON strings like a URL and imports complete Mealie recipe exports or API JSON with full structure for accurate recipe creation.

Instructions

Takes in raw HTML or a https://schema.org/Recipe object as a JSON string and parses it like a URL.

A complete recipe exported from Mealie (the JSON from an export zip, or the recipe as returned by the API) is imported with its full structure instead of being parsed as schema.org.

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": {
      "data": "<data>"
    },
    "name": "create_recipes_create_html_or_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
dataYes
includeTagsNo
accept-languageNo
includeCategoriesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.20.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: input is parsed like a URL, and a complete Mealie export JSON is imported with full structure rather than degraded to schema.org parsing. It says nothing about permissions, duplicate/overwrite behavior, validation failures, or side effects of creating a recipe, which are significant for an unannotated write tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs, front-loaded with the core action, with no filler. The second sentence is slightly convoluted and the awkward line break interrupts flow, but it still earns its place by distinguishing full-structure import from schema.org parsing.

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?

An output schema exists, so return values need not be explained, but for a five-parameter mutation tool with zero annotation and zero schema-description coverage, the description accounts for only one parameter and no operational constraints. An agent could call it with `data` but would have no basis for setting the other four fields.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, and the description only explains `data` (raw HTML or schema.org JSON string). It never explains `url`, `includeTags`, `includeCategories`, or `accept-language` — notably `url` is optional and its role alongside `data` is left entirely unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names concrete input types (raw HTML, a schema.org Recipe JSON string) and states the action (parse like a URL, import as a recipe), so the agent can tell this creates a recipe from inline content rather than a URL. It does not explicitly name its closest siblings (create_recipes_create_url, create_recipes_create_zip, create_recipes_create_html_or_json_stream), so full sibling differentiation is only implied.

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?

Usage is implied rather than stated: 'takes in raw HTML or ... JSON string' suggests this is the tool to pick when you already hold the content instead of a URL, and the second sentence carves out the Mealie-export case. There is no explicit 'use X instead when Y' routing against the many sibling create_recipes_* tools, and no prerequisites are given.

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