Search for available buses between two cities on a specific date. Resolves city names automatically. Use this tool on the HOME page when the user gives route + date + filters in one prompt. Optionally include filter preferences (AC, seat type, departure/arrival slots, operator/brand keyword like Volvo) — they are applied after navigation to the results page. Use runAfterSearchResultsLoad (same shape as runSrpBookingFlow) so open-bus + seat + continue runs automatically after results load — required for multi-step prompts because navigation unloads the home page.
Redbus source site2 tools on this site
What this tool does
Search for available buses between two cities on a specific date. Resolves city names automatically. Use this tool on the HOME page when the user gives route + date + filters in one prompt. Optionally include filter preferences (AC, seat type, departure/arrival slots, operator/brand keyword like Volvo) — they are applied after navigation to the results page. Use runAfterSearchResultsLoad (same shape as runSrpBookingFlow) so open-bus + seat + continue runs automatically after results load — required for multi-step prompts because navigation unloads the home page. Use it on Redbus with an agent. It runs in the browser on the website and needs no package install.
How to install
Open the redbus.in website and ask your browser agent to use searchBuses
Run with an agent
Use the searchBuses tool on redbus.in with source: <string>, destination: <string>, date: <string>, filters: <object>, runAfterSearchResultsLoad: <object>. Return the structured result and cite the source page.
Input contract
sourcestringSource city name (e.g., "Bangalore", "Singapore", "Kuala Lumpur", "Phnom Penh")
destinationstringDestination city name (e.g., "Chennai", "Johor Bahru", "Penang", "Siem Reap")
datestringTravel date. Use ISO YYYY-MM-DD with the correct calendar year (same as the user's "today"). Accepts natural language ("today", "tomorrow") or "in N days". If the year is wrong/outdated, it is corrected to this year or next.
filtersobjectOptional filters to pre-apply on the results page. Include every criterion the user asked for (e.g. AC + SLEEPER + Volvo) in one object.
runAfterSearchResultsLoadobjectOptional. Same fields as runSrpBookingFlow (openBus, selectSeats, continueToBoardingPoints, applyFilters, waitForSearchResultsMs). Stored for the results page to execute after tuples load.
Verify the live listing at the source before a production call. Fields marked as a starter contract may differ from what the site expects.
