HasData

airbnb_listing: GET /

hasdata_airbnb_listing_getAirbnbListings

Read-only

Get Airbnb Listings

Searches Airbnb for available stays by location or map bounding box (neLat/neLng/swLat/swLng) and date range (check-in/check-out) with guest composition (adults, children, infants, pets) and nextPageToken pagination. Returns listing id/url, title, price per night and total, rating, review count, coordinates, and photos. Use for travel planning agents, short-term rental market analysis, pricing/occupancy research, and lead lists for property management.

Input Schema

TableJSON Schema

Name	Required	Description
`pets`	No	Number of pets.
`neLat`	No	North-east corner latitude of the map bounding box. When all four bounding-box coordinates are provided, listings are searched within the box instead of by location.
`neLng`	No	North-east corner longitude of the map bounding box.
`swLat`	No	South-west corner latitude of the map bounding box.
`swLng`	No	South-west corner longitude of the map bounding box.
`adults`	No	Number of adults.
`checkIn`	Yes	The check-in date for the listings.
`infants`	No	Number of infants.
`checkOut`	No	The check-out date for the listings.
`children`	No	Number of children.
`location`	No	The location to search for listings. Required unless a full map bounding box (neLat, neLng, swLat, swLng) is provided.
`nextPageToken`	No	The token used to retrieve the next page of results.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 8, 2026

changedInput schema / properties / location / description

Previous value: -"The location to search for listings."New value: +"The location to search for listings. Required unless a full map bounding box (neLat, neLng, swLat, swLng) is provided."

addedInput schema / properties / neLat

Added value: +{
+  "description": "North-east corner latitude of the map bounding box. When all four bounding-box coordinates are provided, listings are searched within the box instead of by location.\n",
+  "type": "number"
+}

addedInput schema / properties / neLng

Added value: +{
+  "description": "North-east corner longitude of the map bounding box.\n",
+  "type": "number"
+}

addedInput schema / properties / swLat

Added value: +{
+  "description": "South-west corner latitude of the map bounding box.\n",
+  "type": "number"
+}

addedInput schema / properties / swLng

Added value: +{
+  "description": "South-west corner longitude of the map bounding box.\n",
+  "type": "number"
+}

changedInput schema / required

Previous value: -[
-  "location",
-  "checkIn"
-]New value: +[
+  "checkIn"
+]

First observedApr 28, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuine value beyond annotations by disclosing pagination via nextPageToken and listing the returned fields (id/url, price per night and total, rating, reviews, coordinates, photos), which matters since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Lead sentence is front-loaded with the core action and search dimensions, followed by the return payload and use cases. Content is dense but each part contributes; no meaningful padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 parameters at full schema coverage, annotations covering safety, and no output schema, the description usefully compensates by enumerating return fields and pagination. It is essentially complete for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in the schema, including the location-vs-bounding-box interaction. The description adds only a high-level restatement of the search dimensions, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: searches Airbnb for available stays by location/bbox and date range. It is clearly a list/search operation, distinguishable from the sibling getAirbnbPropertyDetails (detail lookup). It does not name or contrast the sibling explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides domain use cases (travel planning, rental market analysis, pricing research, lead lists), which implies when the tool is valuable. However, it offers no when-not-to-use guidance and does not route the agent to the sibling details tool for single-property lookups. Use cases are present but routing guidance is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HasData tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?