My Market Kitchen

Open one Pix Pulse recipe by its experience id — and play it. This renders. Use this to open, watch, or play a specific recipe: when the user asks for one, or names or implies an experience id. It renders a player in the conversation, so call it for the recipe the user wants — not for every candidate you are considering. To let them choose between several, call ``show_recipes`` instead. Returns the full recipe (title, ingredients, method, tags, video URL, related products), and on hosts that support inline apps it renders the recipe as an interactive, playable Pix Pulse experience so the user can watch it right in the conversation. Returns a not-found object if the recipe is not publicly available. Args: experience_id: The integer id of the Pix Pulse experience — from a search_recipes result, or provided by the user.

Find Pix Pulse cooking recipes. Renders nothing — search freely. This tool shows the user nothing, so call it as many times as you need to narrow down. When you have chosen what to show, call ``show_recipes`` with the ids; that is what puts a browsable grid in the conversation. Returns matching recipes with title, ingredients, tags, cooking times, a canonical video URL, related products and an experience id. Cooking method steps are omitted here — ``get_recipe`` returns them. ``facets`` lists the values this catalogue holds for each vocabulary filter, with counts; read them to discover valid values and to widen when a search returns little. ``applied_filters`` and ``unresolved_filters`` report what was understood, ``effective_query`` reports the query actually run when part of ``q`` matched nothing, and ``hint`` names the filter starving a thin result set. Args: q: Free-text keywords, matched against recipe **title, publisher name, description and ingredient lines** — not cooking times, and not the method steps. Prefer short keywords over sentences, and put anything a filter below covers into that filter. Note ``total`` counts recipes matching the filters and at least the first word of ``q``; adding more words re-ranks rather than narrows, so use the filters to narrow. ingredients: Ingredients the recipe must contain, **all of them**, e.g. ["chicken", "potato", "rice"]. Matched against real ingredient lines. This is the way to narrow by ingredient — adding more only ever narrows. (Contrast ``ingredient`` below.) exclude_ingredients: Ingredients the recipe must NOT contain, e.g. ["fish"], ["nuts"], ["dairy"]. The mirror of ``ingredients``: the way to honour a stated allergy or "nothing with X". The allergy umbrellas (fish, shellfish, seafood, nuts, dairy, lactose, gluten, wheat, egg, soy, sesame) expand to the words recipes actually use -- "dairy" also covers butter and cheese, "egg" also covers mayonnaise. Any other term is matched literally against ingredient lines. ``applied_filters`` echoes what was excluded. It does not establish allergy safety or absence of cross-contact, only that tracked ingredient data was filtered. max_total_time_minutes: Only recipes at or under this total time, e.g. 30. About half the catalogue has no recorded time and is excluded; the response reports how many in ``excluded_no_time``. sort: "relevance" (default) or "quickest" — fastest recipes first, untimed ones last. meal: Meal types, e.g. ["Dinner"], ["Breakfast"], ["Dessert"]. occasion: Occasions, including seasons, e.g. ["Spring"], ["Christmas"]. cuisine: Cuisines, e.g. ["Italian"], ["Thai"]. ingredient: Broad primary-ingredient categories from a fixed 24-term taxonomy, e.g. ["Chicken recipes"]. Values here are combined with OR — passing several **widens** the search. To require several ingredients together, use ``ingredients`` above. diet: Dietary styles, e.g. ["Vegetarian recipes"], ["Gluten-free recipes"]. cooking_method: Methods, e.g. ["Baking recipes"], ["Air fryer recipes"]. meal_ids: Numeric ids, if you already hold them. Prefer the string filters above — ids are an internal detail. occasion_ids: Numeric ids, as above. cuisine_ids: Numeric ids, as above. ingredient_ids: Numeric ids, as above. limit: Maximum number of results to return (1-50, default 12).

Show several recipes to the user as a browsable grid. This renders. Call this once you have decided what to show, with the ids from ``search_recipes``. The grid displays them in the order given. **For a single recipe, call ``get_recipe`` instead** — it plays the recipe rather than showing one card the user has to click. **Pass 6, 3 or 2 ids.** The grid renders 6 when given 6, 3 when given 3 to 5, and otherwise all of them — so 4 or 5 ids show only 3. Anything trimmed is reported in ``omitted``, and ``displayed`` is what the user can actually see: describe those, not the ones that were trimmed. Ids that are not publicly available come back in ``unavailable`` rather than silently thinning the grid. Args: experience_ids: Experience ids to show, in the order to show them.