We built something like this too (in a different field), but it's actually quit hard to deal with all the edge cases that people might want to search for:
e.g. if the user asks "Find hotels in Capetown [...] that have availability for this christmas or new year": if your backend, or the response format that you're forcing the LLM to give, doesn't have the ability to do an OR on the date range, you can't give results that the user wants, so the LLM tries to do as best it can, and the user ends up getting only hotels which are available for both Christmas and new year (thus missing some that have availability for one or the other), or the LLM does some other unwanted thing. For us, users would even ask "June or August", and then got July included because that was the closest thing the backend / UI could do.
So this approach is actually less flexible than a chat interface, where the LLM can figure out "Ah, I need to do two separate hotel search MCP calls, and then merge the results to not show the same hotel twice".
We didn't support the time dimensions, but I think it could be done without too much issue. You suggest displaying search results in a chat interface but that doesn't work because there are easily hundreds of hotel results for most searches. The user would need to click on a thumbnail in chat into the list of search results on the OTA.
e.g. if the user asks "Find hotels in Capetown [...] that have availability for this christmas or new year": if your backend, or the response format that you're forcing the LLM to give, doesn't have the ability to do an OR on the date range, you can't give results that the user wants, so the LLM tries to do as best it can, and the user ends up getting only hotels which are available for both Christmas and new year (thus missing some that have availability for one or the other), or the LLM does some other unwanted thing. For us, users would even ask "June or August", and then got July included because that was the closest thing the backend / UI could do.
So this approach is actually less flexible than a chat interface, where the LLM can figure out "Ah, I need to do two separate hotel search MCP calls, and then merge the results to not show the same hotel twice".