mcp-server-airbnb
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISABLE_GEOCODING | No | Skip the Photon/Nominatim geocoding step and let Airbnb resolve the location string on its own. | false |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| airbnb_searchA | 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 completely distinct purposes: one searches for listings, the other gets details for a specific listing. No overlap or ambiguity.
Both tool names follow the same 'airbnb_<action>' pattern using snake_case, making them predictable and consistent.
With only 2 tools, the server is minimal. While it covers essential search and detail retrieval, it may feel thin for a comprehensive Airbnb integration, but it is borderline acceptable.
Major functionality is missing: no booking, no user reviews, no listing management. The tool surface is very limited for the Airbnb domain.