Skip to main content
Glama

Import recipe

import_recipe
Idempotent

Use this when the user pastes a recipe link (any recipe site, Instagram, TikTok, YouTube, Pinterest or Facebook) and wants the recipe itself. Returns clean ingredients and steps without ads. Does not add anything to the user's account; call save_recipe afterwards if they want to keep it. For recipe text pasted into the chat, use create_recipe instead.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to import the recipe from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false, idempotentHint=true and openWorldHint=true, so the description's job is to clarify the readOnlyHint=false flag, which it does well by stating it does not add anything to the user's account. It also describes the return content (ingredients and steps, no ads). It does not cover failure modes, such as an unsupported or unreachable URL, or any rate/limits on fetching.

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?

Four short sentences, front-loaded with the trigger condition, then output, side effects, and the alternative. No filler or restated title text; each sentence adds a distinct decision-relevant fact.

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?

With no output schema, the description appropriately summarizes the return value rather than leaving it opaque, and it clarifies persistence semantics for a non-read-only tool. The remaining gap is error behavior when a link is unsupported or unfetchable, which is minor for a one-parameter tool.

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?

Schema coverage is 100% for the single url parameter, so the schema already carries the mechanics. The description still adds real meaning by listing which sources the URL may point at, which is information absent from the schema and relevant when deciding whether to call the tool at all.

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?

"Import a recipe from a pasted link and return clean ingredients and steps" gives a specific verb, resource, and output. It also enumerates the accepted sources (recipe sites, Instagram, TikTok, YouTube, Pinterest, Facebook), which is the main thing distinguishing it from text-based siblings.

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?

Explicit trigger ("when the user pastes a recipe link... and wants the recipe itself"), an explicit exclusion with the correct alternative ("For recipe text pasted into the chat, use create_recipe instead"), and a stated follow-up (call save_recipe if they want to keep it). Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources