Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_airbnb_nearby

Retrieve Airbnb market density near a coordinate. Returns a geohash-grid density map with listing count and Superhost share per cell.

Instructions

Airbnb market density near a coordinate. Returns an aggregate geohash-grid density map of Airbnb listings within a radius of a coordinate, from dataset id enum value airbnb-markets. Each cell reports a centroid, listing count and Superhost share; thin cells are suppressed. Aggregate-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesCenter latitude, from -90 through 90
lonYesCenter longitude, from -180 through 180
countryNoExact ISO-3166-1 alpha-2 country filter, e.g. US
radius_mYesSearch radius in meters, from 1 through 50000
precisionNoGeohash precision, from 1 through 12; defaults to a value derived from the radius
superhostNoCount only Superhost listings
min_ratingNoMinimum listing rating, from 0 through 5
active_sinceNoFreshness filter, an ISO-8601 date (YYYY-MM-DD)
min_listingsNoMinimum listings per cell; raises the small-cell suppression floor
Behavior4/5

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

With no annotations, the description fully carries the burden. It describes the output fields (centroid, listing count, Superhost share) and behavior (thin cells suppressed). It does not mention permissions or side effects, but the tool appears to be read-only and safe.

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?

Two sentences with no wasted words: first sentence defines the tool's purpose and output type, second adds details on output fields and behavior.

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?

The description covers the main output and behavior. With no output schema, it adequately describes what is returned. It could explicitly state that it does not return individual listings, but 'aggregate-only' implies this.

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

Parameters4/5

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

Schema coverage is 100%, providing baseline 3. The description adds context about the geohash grid and aggregation, and notes that thin cells are suppressed, adding value beyond the schema.

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

Purpose5/5

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

Description clearly states it returns an aggregate geohash-grid density map of Airbnb listings near a coordinate, from a specific dataset. This distinguishes it from sibling tools like `airbnb_search` which return individual listings.

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

Usage Guidelines4/5

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

The description specifies that it returns aggregate data only ('Aggregate-only'), indicating it is not for individual listing details. It does not explicitly list alternatives or when not to use, but the context from sibling tools and the description provide sufficient guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server