Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

Import recipe from URL

import_recipe_from_url

Import recipes from URLs into Tandoor using built-in scraping with JSON-LD fallback, and optionally create a placeholder recipe when extraction fails.

Instructions

Import a recipe from a URL. Tries Tandoor's built-in scraper first, then fetches the page and extracts schema.org JSON-LD as a real fallback (works when Tandoor can't reach the URL or doesn't support the site). On total failure, throws with an attempts log; pass create_stub_on_failure=true to write an empty placeholder recipe instead. If all stages fail, recommend: (1) retry with create_stub_on_failure=true to capture the URL as a stub you can fill in later; (2) if the page is an image/PDF, use import_recipe_from_image (AI provider required); (3) if the URL is paywalled or JS-rendered, fall back to manual create_recipe with fields you can see.

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": {
      "url": "<url>"
    },
    "name": "import_recipe_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRecipe URL to import
nameNoOptional name for the stub recipe (only used if create_stub_on_failure=true and both scrapers fail)
formatNoResponse detail level. Default "slim".
create_stub_on_failureNoDefault false. When true AND both scraper attempts fail, create a minimal empty recipe pointing at the URL instead of throwing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the ordered scraper fallback chain, throw-with-attempts-log failure semantics, and the opt-in stub-write behavior when create_stub_on_failure is true. What is not covered is the write side effect implied by readOnlyHint=false — whether a repeat import creates a duplicate recipe (idempotentHint is false) and whether the target space/auth scope matters. Strong, but the mutation behavior is only partly disclosed.

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?

Front-loaded with the primary action and fallback chain, and the numbered failure-recovery guidance is easy to scan. There is minor redundancy: the total-failure/throw condition is stated twice, first inline and again as step (1) of the recommendations.

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?

For a multi-stage import with side effects, the description covers success paths, failure paths, and recovery options thoroughly. The remaining gap is that with no output schema, nothing explains what a successful import returns (e.g., the recipe body subject to format=slim/full), and the write side effect of creating a recipe is only implicit.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents url, name, format, and create_stub_on_failure, including the stub-scoping of name. The description reinforces create_stub_on_failure's conditional behavior but says nothing about format's slim vs full response or the url format expectations, so it adds little beyond the schema baseline.

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 states a specific verb and resource ('Import a recipe from a URL') and immediately clarifies the mechanism and scope: built-in scraper first, then a JSON-LD fallback. It also names the sibling tools it is not (import_recipe_from_image, create_recipe), so an agent can distinguish it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent across alternatives: retry with create_stub_on_failure for a placeholder, use import_recipe_from_image for image/PDF sources (with the AI-provider caveat), and fall back to manual create_recipe for paywalled or JS-rendered pages. Both when-to-use and when-not-to-use are covered, with conditions attached to each path.

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