Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

airbnb_search

Search public Airbnb stays by location, check-in/out dates, guests, and map area. Returns listings with price, rating, host, and Superhost/Guest Favorite flags.

Instructions

Search Airbnb stays. Searches public Airbnb stays for a location, with optional check-in and check-out dates, adult count, currency and page. Pass ne_lat, ne_lng, sw_lat and sw_lng to bound the search to a map area. Each result has the listing id, title, URL, location and coordinates, price and price per night, rating, review count, host, and the Superhost and Guest Favorite flags.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page
zoomNoMap zoom for bounded map search
adultsNoAdult guests
ne_latNoNortheast latitude for bounded map search
ne_lngNoNortheast longitude for bounded map search
sw_latNoSouthwest latitude for bounded map search
sw_lngNoSouthwest longitude for bounded map search
check_inNoCheck-in date
currencyNoCurrency for bounded map search
locationYesLocation
check_outNoCheck-out date

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers by enumerating the result shape: listing id, title, URL, location/coordinates, price and price-per-night, rating, review count, host, plus Superhost and Guest Favorite flags. That is strong behavioral disclosure given no output schema. It still omits auth requirements, rate limits, and pagination semantics beyond the bare page param.

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

Conciseness5/5

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

Three front-loaded sentences: purpose first, then optional filters and map bounding, then return shape. Every sentence earns its place and there is no filler.

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?

For an 11-param search tool with no annotations and no output schema, the description covers purpose, key filters, map bounding, and the full return shape. Minor gaps remain (zoom behavior, pagination limits, date format), but nothing critical to correct invocation is missing.

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 the schema already documents all 11 parameters; baseline is 3. The description adds marginal meaning by grouping the geo params into a 'map area' concept, but it omits zoom and adds no format details (e.g., date format, currency codes) beyond what the schema provides.

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: 'Search Airbnb stays' / 'Searches public Airbnb stays for a location'. The scope word 'public' adds useful qualification. It does not, however, explicitly distinguish itself from close siblings like airbnb_room or datasets_airbnb_search, 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?

The description explains the optional filters and how to bound a map search ('Pass ne_lat, ne_lng, sw_lat and sw_lng to bound the search to a map area'), which is a usage hint. But it never states when to prefer this tool over airbnb_room (detail), airbnb_room_reviews, or datasets_airbnb_search, and gives no exclusions or prerequisites.

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

Deploy Server

Other Tools