get_recipe
Retrieve cocktail recipes by name or ID, supporting single requests or batch processing for multiple drinks with parallel fetching and error isolation.
Instructions
🍸 Advanced recipe retrieval with powerful batch processing for multiple cocktails.
🚀 BATCH PROCESSING SYSTEM:
High Performance: 5-10x faster than sequential requests
Parallel Processing: Simultaneous API calls with error isolation
Smart Caching: 70%+ cache hit rate for repeated requests
Flexible Input: Mix cocktail names and IDs in single request
Error Resilience: Individual failures don't break entire batch
📋 LLM Usage Patterns:
Single Recipe: When user asks for "how to make [cocktail]"
Recipe Comparison: When user wants to compare multiple cocktails
Menu Planning: Batch retrieve recipes for event planning
Variation Exploration: Get base recipe + similar cocktails
Research Mode: Efficient lookup of multiple specific recipes
🎯 Input Methods (Choose Based on Use Case):
Single Recipe (Backwards Compatible):
cocktail_name: "Manhattan" → One complete recipe
cocktail_id: 123 → Recipe by database ID
Batch by Names (Most Common):
cocktail_names: ["Negroni", "Manhattan", "Martini"] → Multiple complete recipes
Batch by IDs (When Available):
cocktail_ids: [1, 2, 3] → Multiple recipes by database IDs
Mixed Batch (Maximum Flexibility):
cocktail_names: ["Aviation"] + cocktail_ids: [123, 456] → Combined approach
With Variations (Exploration):
Any above + include_variations: true → Base recipes + similar cocktails
📊 Response Format: Structured output with complete recipe data:
Precise ingredient measurements (auto-converted to oz)
Step-by-step preparation instructions
Cocktail specifications (ABV, glassware, method, garnish)
Direct database links for each recipe
Performance metrics (timing, cache usage)
Similar recipes when requested
Rich formatting with emojis and clear sections
⚡ Performance Examples:
Single recipe: ~150-300ms (cached responses faster)
Batch (3 cocktails): ~250-400ms (vs 900ms+ sequential)
Mixed batch (5 cocktails): ~300-500ms with parallel processing
Cache hit: <50ms instant response
🎛️ Batch Control Parameters:
limit: 1-20 recipes (default: 10) - controls batch size
include_variations: Boolean - adds similar cocktails to results
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cocktail_id | No | 🆔 Single cocktail database ID. Use for specific recipe lookup when ID is known. | |
| cocktail_name | No | 🍸 Single cocktail name. Use for individual recipe requests (e.g., "Manhattan", "Negroni"). | |
| cocktail_ids | No | 🚀 Array of cocktail IDs for batch processing. Enables parallel retrieval of multiple recipes by database ID. More efficient than multiple single requests. | |
| cocktail_names | No | 🚀 Array of cocktail names for batch processing. Enables parallel retrieval of multiple recipes by name (e.g., ["Manhattan", "Negroni", "Martini"]). Triggers name resolution + batch fetching. | |
| include_variations | No | 🔄 Include similar/variation recipes in results. Adds related cocktails to expand exploration (default: false). | |
| limit | No | 🎛️ Maximum number of recipes to return. Controls batch size for optimal performance (default: 10, max: 20). Higher limits may impact response time. |