Airbnb Search & Listings
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| airbnb_searchC | Search for Airbnb listings with various filters and pagination. Provide direct links to the user |
| airbnb_listing_detailsC | Get detailed information about a specific Airbnb listing. Provide direct links to the user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves detailed information for a specific listing, while the other searches for listings with filters. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool.
Both tools follow a consistent 'airbnb_' prefix and descriptive naming pattern (airbnb_listing_details and airbnb_search). This predictability enhances readability and reduces confusion for agents.
With only 2 tools, the server feels thin for a domain like Airbnb search and listings. It lacks essential operations such as booking, user management, or listing creation, which are core to the Airbnb experience, making the scope incomplete.
The tool surface is severely incomplete for the server's purpose. While search and details are foundational, there are significant gaps in operations like booking, payment, reviews, or host interactions, which will likely cause agent failures in real-world scenarios.