Chop it

Use this when the user wants a shopping list from recipes or a meal plan — combining ingredients from several recipes into one consolidated, aisle-organised grocery list, scaled to their servings. Takes a menu draft (menuDraftId) or a set of recipes (recipeIds), merges duplicate ingredients across recipes, and returns a shoppingListId for handoff to an online shop.

create_shopping_list

Use this when the user wants to plan dinners for the week, wants a weekly meal plan (cheap family dinners, healthy or high-fibre weeks, more plants, working toward 30 plants a week), or wants to reduce food waste by planning around overlapping ingredients or what's in their pantry. Builds a draft week from Chop It's catalogue using the app's recipe ranking (pantry-aware when the caller has pantry items). Returns a draft (menuDraftId) you can pass to create_shopping_list, with a per-recipe appUrl on every dinner. Only dinner-suitable mains are picked (never sides, dips, starters or lunches). ALWAYS pass dietary/maxTimeMins when the user implies them — they are hard constraints; the server also parses the brief text as a fallback. Does not save anything to the user's account in this version.

create_weekly_menu

Use this when the user asks how to make a dish, wants to start cooking tonight's dinner, or asks for the full recipe with quantities and steps. Fetches the complete recipe — ingredients and step-by-step method — by recipeId (from search_recipes, create_weekly_menu, or list_saved_recipes). Works for catalogue recipes and the user's own saved recipes. Read-only.

get_recipe

Use this when the user wants to save a recipe from TikTok, save an Instagram recipe, or import a recipe from any website link so it isn't lost — turning saved-but-never-cooked links into recipes they can plan and shop. Also accepts pasted caption text when a link can't be fetched. The server extracts the source, restructures it through Chop It's canonical recipe pipeline, and saves it to their library. If the result is needs_review, show the preview to the user, fix the flagged issues together, and save the corrected version with save_recipe. Limited per conversation.

import_recipe_from_url

Use this when the user wants to digitise a recipe from a photo — importing a cookbook page, a recipe screenshot, or a handwritten family recipe card into their Chop It library. Pass a fetchable http(s) image URL. The server reads the photo, restructures it through Chop It's canonical recipe pipeline, and saves it. If the result is needs_review, show the preview to the user, fix the flagged issues together, and save the corrected version with save_recipe. If the image URL can't be fetched, ask the user to paste the recipe text and use import_recipe_from_url with a caption instead. Limited per conversation.

import_recipe_from_image

Use this when the user asks what recipes they've saved, wants to browse their recipe library, or wants to plan a week from recipes they've already collected. With a connected Chop It account this is their full app library; without one it lists what was saved in this conversation (which lives here until claimed via keep-links). Read-only.

list_saved_recipes

Use this when the user wants to shop their list online — sending the shopping list to their supermarket basket (Tesco, Sainsbury's, Asda and other UK retailers via Whisk) or opening it in the Chop It app. Takes a shopping list (shoppingListId) or menu draft (menuDraftId) and returns links only. This does NOT complete checkout and does not buy anything — the user picks a retailer and pays there.

open_shop_handoff

Use this when the user wants to keep a recipe: one from a cookbook page you've read with vision, one they invented or developed with your help, or corrected output from an import. Saves a fully structured recipe to their Chop It library. Requirements before saving: UK ingredient vocabulary and metric quantities, ingredients grouped into logical sections, a complete method with sensory cues, and a title without marketing words. With a connected Chop It account the save is permanent (keepUrl is null). Without one, returns a keepUrl the user should open in the Chop It app and tap 'Save to My Recipes' to keep the recipe permanently — always share that link when present.

save_recipe

Use this when the user wants recipe or dinner ideas: quick dinners under 30 minutes, meals matching a dietary need (vegetarian, vegan, high fibre, healthy), a specific protein or cuisine, or what they can cook with ingredients they already have. Searches Chop It's catalogue of 1,000+ tested recipes and returns cards (title, image, time, tags, protein) with links into the app. Read-only. ALWAYS pass structured filters when the request implies them — 'quick chicken dinners' → filters.protein ['chicken'] + filters.maxTimeMins 30. Filters are hard constraints; the server also parses the query text (protein, time, dietary, dinner intent) as a fallback, and dinner-intent queries exclude sides, dips and starters.

search_recipes

Use this when the user asks what they can cook with what they have, wants to use up ingredients before they go off, or wants meals planned around what's already in the fridge and cupboards. Lists the caller's Chop It pantry (name, storage location, quantity, how full, expiry) — for a linked account, the same pantry the app shows. Check it before planning to build the week around what's already in the kitchen, and mention items that are low or close to expiry.

get_pantry