Import a recipe from a URL by scraping the page, letting Mealie extract the recipe data automatically. Use this to add recipes from web pages directly.
Import a recipe by scraping a URL. Mealie will extract the recipe data automatically.
Args: url: URL of the recipe page to import
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
It discloses the core behavior: the tool scrapes a URL and automatically extracts recipe data, which is useful context. However, with no annotations, the description carries the full burden and does not mention auth requirements, duplicate handling, or the full side effect profile of importing a recipe.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and well-structured: two purposeful sentences plus a minimal Args block. The main purpose is front-loaded and there is no fluff or redundant restatement of the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter import tool with an output schema present, the description covers the tool's purpose and its required input well. It does not address usage exclusions or edge cases, but the tool's simplicity limits how much additional context is necessary.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema only says url is a string, so the description's Args block adds meaningful semantics: 'URL of the recipe page to import.' For a single-parameter tool, this sufficiently compensates for 0% schema coverage, though it could mention format constraints such as public URL requirements.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Import a recipe by scraping a URL.' It clearly identifies the URL-based import mechanism, which distinguishes it from the sibling create_recipe tool, though it does not explicitly name that alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the use case—providing a recipe page URL and having Mealie extract the data—but it does not explicitly state when to prefer this over create_recipe or when not to use it. No exclusions or alternative routing are present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.