MakeMyTrip
Description
Discover flights and hotels with real time inventory and pricing right inside your conversation.
Capabilities
Publisher Intelligence
Insights and recommendations for app publishers. See how your app performs and how to improve discoverability.
Server Status make-my-trip v1.0.0
https://www.makemytrip.com/ai/mcp?src=cm Last checked: 23h ago
Technical Details
Tools(5)
Showing 5 of 5 tools
| Tool | Description | Flags | Test | Last Tested | |
|---|---|---|---|---|---|
fetch-cabs | Search available cabs between source and destination. Supports optional filters (cab type, fuel type, seats, luggage, AC, price range) and sorting (cheapest, priciest, rating). Include filters when the user specifies preferences like 'CNG cab', 'cab for 4 passengers', 'cheapest option', or 'luxury cab', both in initial requests and follow-ups. IMPORTANT: Before calling this tool, you MUST first resolve both source and destination locations using the resolve-cab-location tool to get their place_ids. Do NOT call this tool without valid place_ids from resolve-cab-location. Always ask the user explicitly for: travel date and pickup time. Never use default or assumed values for date and time - the user must provide them. If the response has status 'no_cabs_found', apologize politely and share the message and suggestion. Never say 'server error' or show raw error codes to the user. | read-only | 75%Latency 4.1s | May 11, 2026 | |
fetch-flight-fare-calendar | Fetch approximate lowest fares across dates (fare calendar) on MakeMyTrip. Pass the exact `it` string for the fare calendar API (same as MMT fareCalendar query param). Typical outbound form: ORIG-DEST-YYYYMMDD. For RT, use the outbound `it` MMT expects and set isRoundTrip true (adds tripType=RT). Prices are indicative; final fares on MakeMyTrip may differ. | read-only | 100%Latency 564ms | 22h ago | |
fetch-flights | Fetch the flight listing for the given departure city and destination city | read-only | 100%Latency 349ms | May 11, 2026 | |
fetch-hotels | Get hotel search results by first using autosuggest to find the city code, then fetching hotel listings for that city | read-only | 50%Latency 7.8s | May 11, 2026 | |
resolve-cab-location | Resolve a pickup or drop-off location for cab booking. Call this tool BEFORE fetch-cabs to get the place_id for each location. For city or town level queries (e.g., 'Bangalore', 'Mysore', 'Delhi'), the tool auto-resolves to the best match — no disambiguation step is needed. For specific locations (neighborhoods, airports, railway stations, tech parks), multiple matches may be returned for the user to choose from. If the user provides both source and destination in their message, resolve both locations without waiting — do NOT ask for the second one again. Do NOT suggest or guess location names yourself — ALWAYS call this tool to get real options. Never present your own list of guessed locations. If multiple matches are found, present the numbered options to the user and ask them to pick one (or say 'none' for a different location). Then call this tool again with the selected place_id. Once both source and destination place_ids are resolved, call fetch-cabs with them. | read-only | 75%Latency 4.1s | May 11, 2026 |
Discoverability Score
Fair
57 of 100 — how easily AI agents find your app
- Description quality14/20
- Example prompts0/20
- Keyword coverage0/15
- Tool metadata20/20
- Visual assets13/20
- Endpoint health10/10
- Data freshness11/15
How to Improve
Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.
Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.
Add at least 2 screenshots that show real workflows to increase confidence and conversion.
Technical Details
- Status
- ENABLED
- Type
- AI-Powered App
- Auth
- Open Access
- Listed on
- ChatGPT
- Added
- February 14, 2026
- Last synced
- May 3, 2026
- Last checked
- 23h ago
- Version
- 1.0.0
- Distribution
- Ecosystem Directory