Ticketek

Return a Ticketek booking URL for a show or a specific performance instance.

tickets.link

List the currently known performance instances for a single Ticketek show. Use this when the user wants to choose a specific session after selecting a show.

instances.list

Search Ticketek shows with one consolidated call per user query. Combine all extracted constraints (location, date_filter, category, artist/show/venue, and preferences) into that single call. Use `search` only for short keyword tags (artist/show/venue/genre nouns), not long natural-language sentences. For broad discovery requests primarily driven by location/date/category (for example 'what's on in Sydney this weekend'), omit `search` entirely and let structured constraints drive retrieval. Do not split one user request into multiple `shows.search` calls by category; the response is already unified and ranked. When `results[].purchase_url` or `results[].next_instance.purchase_url` is present, render clickable purchase links directly in the user response first. Always use markdown links with descriptive anchor text (never bare URLs): use show title for show-level links, session date/time label for session-specific links, and fallback to short anchors like `Buy tickets` or `View session details` if title/date is unavailable. Use `shows.detail` and `instances.list` for richer context/session choice when the user asks, and use `tickets.link` only when no direct purchase URL is available.

shows.search

Fetch detailed information for one Ticketek show, including full description, lead instance, and handoff metadata. Use this after selecting a show from search results.

shows.detail