Crawlora MCP

datasets_airbnb_hosts_facets

Read-only

Returns host counts grouped by superhost, identity_verified, listing_count_band, hosting_years_band, interest, verification or location, honoring the same filters as search. Use it to size or compare a segment of Airbnb hosts before running datasets_airbnb_hosts_search.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "facet": "<facet>"
    },
    "name": "datasets_airbnb_hosts_facets"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional full-text query over host name and bio, max 256 characters.
`page`	No	Result page number, 1-based, default 1; page times page_size must not exceed 10000.
`sort`	No	Optional sort order. Allowed values: review_count_desc, listing_count_desc, hosting_years_desc, relevance. Defaults to relevance with q, otherwise review_count_desc.
`facet`	Yes	Required facet to aggregate. Allowed values: superhost, identity_verified, listing_count_band, hosting_years_band, interest, verification, location.
`interest`	No	Optional exact interest, as returned by the interest facet, e.g. Architecture.
`location`	No	Optional free-text match over the profile location, e.g. Portugal or Lisbon. Every word must match. Hosts write this field themselves, so spellings vary.
`page_size`	No	Page size, default 20, max 100; page times page_size must not exceed 10000.
`min_reviews`	No	Optional minimum total guest reviews received, 0 or greater.
`is_home_host`	No	Optional filter on the home-host flag.
`is_superhost`	No	Optional filter: true keeps only Superhosts, false keeps only hosts without the badge.
`max_listings`	No	Optional maximum number of listings the host manages, 0 or greater.
`min_listings`	No	Optional minimum number of listings the host manages, 0 or greater.
`verification`	No	Optional exact verification, as returned by the verification facet, e.g. Identity.
`identity_verified`	No	Optional filter: true keeps only hosts whose identity is verified.
`min_hosting_years`	No	Optional minimum years of hosting, 0 or greater.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and an output schema exists, so the description is not carrying the safety or return-shape burden. It still adds real context beyond the structured fields: the operation is a counting/grouping aggregation and it honors 'the same filters as search,' which tells the agent the filter semantics are shared with the sibling tool. It omits anything about how page/page_size interact with an aggregated facet result, which is the one behavioral gap.

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, zero waste, and the core output ('host counts grouped by ...') is front-loaded ahead of the workflow advice. Nothing is repeated for 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?

For a 15-parameter aggregation tool with a full output schema and safety annotations, the description covers purpose, workflow position, and filter inheritance adequately. The only unaddressed complexity is why pagination parameters exist on a facet aggregation, which an agent might reasonably wonder about.

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 coverage is 100%, so the per-parameter meanings are already documented in the input schema and the baseline is 3. The description adds marginal value by noting the filters behave like the search tool's filters, but the facet enumeration in the text merely restates the `facet` enum already in 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?

The description uses a specific verb and resource ('Returns host counts grouped by superhost, identity_verified, ...') and enumerates the facet dimensions, so it is unmistakably an aggregation tool rather than a record-list tool. It also names the sibling it complements (datasets_airbnb_hosts_search), which distinguishes it from both hosts_search and the datasets_airbnb_facets sibling.

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?

It gives explicit workflow guidance: use it to 'size or compare a segment of Airbnb hosts before running datasets_airbnb_hosts_search.' That tells an agent both the use case and the ordering relative to the search tool. It stops short of stating when NOT to use it (e.g. when per-host records are needed, skip straight to search), so it is strong but not complete.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.