Airbnb MCP Server
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 and pagination. There is no overlap or ambiguity between them.
Both tools follow a consistent 'airbnb_' prefix and descriptive naming pattern (airbnb_listing_details, airbnb_search). The naming is uniform and predictable across the set.
With only two tools, the server feels thin for an Airbnb domain, which typically involves operations like booking, reviews, user management, or listing updates. The current set is too limited for comprehensive coverage.
The server covers basic search and details retrieval but lacks essential operations such as booking, payment, user authentication, or listing management. This creates significant gaps that will likely cause agent failures in real-world scenarios.