Provides tools for searching Airbnb listings with advanced filters and pagination, and retrieving detailed information about specific listings for travel planning and research.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Airbnb-Search search for 2-bedroom apartments in Tokyo for next weekend"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
一个提供高级筛选功能和详细房源信息的Airbnb搜索桌面扩展，适用于旅行规划和房源研究。 An Airbnb search desktop extension that offers advanced filtering features and detailed listing information, suitable for travel planning and listing research.## 工具列表 Tool List
本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。
工具 Tool | 描述 Description |
airbnb_search | Search for Airbnb listings with various filters and pagination. Provide direct links to the user |
airbnb_listing_details | Get detailed information about a specific Airbnb listing. Provide direct links to the user |
工具在线测试： https://mcp.xiaobenyang.com/inspector/1777316659557379
Online Tool test https://mcp.xiaobenyang.com/inspector/1777316659557379
Related MCP server: Airbnb MCP Server
如何获取 XBY-APIKEY ？ How to get XBY-APIKEY ?
访问小笨羊科技网站 https://xiaobenyang.com，注册用户即可获得APIKEY Visit XiaoBenYang website https://xiaobenyang.com, register and get the APIKEY.
{
"mcpServers": {
"Airbnb搜索扩展": {
"headers": {
"XBY-APIKEY": "<YOUR_XBY_APIKEY>"
},
"type": "sse",
"url": "https://mcp.xiaobenyang.com/1777316659557379/sse"
}
}
}{
"mcpServers": {
"Airbnb搜索扩展": {
"headers": {
"XBY-APIKEY": "<YOUR_XBY_APIKEY>"
},
"type": "streamable_http",
"url": "https://mcp.xiaobenyang.com/1777316659557379/mcp"
}
}
}{
"mcpServers": {
"Airbnb搜索扩展": {
"command": "npx",
"args": [
"-y",
"xiaobenyang-mcp"
],
"env": {
"XBY_APIKEY": "<YOUR_XBY_APIKEY>",
"mcpId": "1777316659557379",
},
"transport": "stdio"
}
}
}
Get detailed information about a specific Airbnb listing. Provide direct links to the user
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| checkin | No | ||
| checkout | No | ||
| adults | No | ||
| children | No | ||
| infants | No | ||
| pets | No | ||
| ignoreRobotsText | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions 'Get detailed information' and 'Provide direct links,' which implies a read-only operation, but it doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what 'detailed information' includes. For a tool with 8 parameters and no annotations, this is a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized and front-loaded: two concise sentences that directly state the tool's purpose and a key usage note. Every sentence earns its place without redundancy or fluff, making it efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (8 parameters, no annotations, no output schema), the description is incomplete. It lacks details on parameter usage, return values, error conditions, and behavioral constraints. While it states the purpose clearly, it doesn't provide enough context for an agent to effectively use the tool without guesswork, especially with undocumented parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, meaning none of the 8 parameters are documented in the schema. The description does not add any meaning beyond the schema—it doesn't explain what parameters like 'ignoreRobotsText' do, how dates should be formatted, or the purpose of occupancy fields. With low coverage and no compensation in the description, this fails to provide necessary parameter context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get detailed information about a specific Airbnb listing.' It specifies the verb ('Get') and resource ('Airbnb listing'), and distinguishes it from the sibling tool 'airbnb_search' by focusing on details for a specific listing rather than searching. However, it doesn't explicitly differentiate from the sibling beyond implied scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides minimal guidance: 'Provide direct links to the user' hints at usage context, but it doesn't specify when to use this tool versus 'airbnb_search' or other alternatives, nor does it mention prerequisites or exclusions. No explicit when/when-not instructions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search for Airbnb listings with various filters and pagination. Provide direct links to the user
| Name | Required | Description | Default |
|---|---|---|---|
| location | Yes | ||
| placeId | No | ||
| checkin | No | ||
| checkout | No | ||
| adults | No | ||
| children | No | ||
| infants | No | ||
| pets | No | ||
| minPrice | No | ||
| maxPrice | No | ||
| cursor | No | ||
| ignoreRobotsText | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'pagination' (via the cursor parameter) and 'direct links to the user', which adds some context beyond the schema. However, it lacks critical details like rate limits, authentication needs, error handling, or what the search results look like (e.g., format, size limits). For a search tool with 12 parameters and no annotations, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose ('Search for Airbnb listings') and adds key details ('with various filters and pagination. Provide direct links to the user'). There's no wasted text, and it's appropriately sized for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (12 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the output format, error conditions, or provide enough behavioral context for safe and effective use. The mention of 'direct links' is helpful but insufficient to cover the gaps in parameter documentation and behavioral transparency.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It mentions 'various filters' which hints at parameters like location, dates, and price, but doesn't explain any specific parameters (e.g., what 'placeId' vs 'location' means, format for 'checkin'/'checkout', what 'ignoreRobotsText' does). With 12 undocumented parameters, the description adds minimal semantic value beyond the schema's property names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Search') and resource ('Airbnb listings'), and mentions filters and pagination which differentiates it from the sibling tool 'airbnb_listing_details' that likely fetches details for a specific listing. However, it doesn't explicitly contrast with the sibling tool, so it's not a perfect 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions 'various filters and pagination' which implies usage for searching, but provides no explicit guidance on when to use this tool versus 'airbnb_listing_details' or other alternatives. There's no mention of prerequisites, constraints, or specific scenarios for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
airbnb_listing_detailsairbnb_searchThe two tools have clearly distinct purposes: one retrieves details for a specific listing, while the other searches across multiple listings with filters. There is no overlap in functionality, making it easy for an agent to choose the right tool based on whether it needs specific data or a broader search.
Both tools follow a consistent naming pattern with the prefix 'airbnb_' followed by a descriptive verb_noun combination (listing_details and search). This uniformity enhances readability and predictability, making the tool set easy to navigate.
With only two tools, the server feels under-scoped for an Airbnb search domain. While the tools cover basic search and detail retrieval, there are likely missing operations such as booking, user reviews, or availability checks, which could limit agent effectiveness in handling comprehensive Airbnb-related tasks.
The tool set is severely incomplete for an Airbnb domain. It lacks essential operations like booking a listing, checking availability, managing reservations, or accessing user reviews. This creates significant gaps that will likely cause agent failures when trying to perform common Airbnb workflows beyond simple searching and viewing details.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Searchable directory of Airbnb listings — discover properties and retrieve direct Airbnb links.
Airbnb stays by location and dates, and full listing details, as structured JSON.
Airbnb & short-term rental market analytics: occupancy, ADR, RevPAR, revenue, comparables.
Vacation rental discovery, direct booking, and property protection for AI agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/xiaobenyang-com/1777316659557379'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
