Crawlora MCP

datasets_airbnb_hosts_search

Read-only

Searches the Airbnb hosts dataset and returns public host profiles with name, location, bio, Superhost and identity-verification status, hosting tenure, review count and listing count. Use it to find or rank hosts by text, location, Superhost status, number of listings or reviews, then call datasets_airbnb_hosts_item for one host.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "datasets_airbnb_hosts_search"
  }
}

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.
`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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds that results are public host profiles and lists which fields come back, which is useful. Pagination ceilings and the page*page_size limit live only in the schema, and there is no note on whether some filters come from facet values.

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 filler, with the capability and return shape front-loaded and the follow-up action placed last where an agent will look for next steps.

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 14-parameter search tool with an output schema, the description covers purpose, queryable dimensions, and the natural next call. Minor gaps remain around facet-derived values and pagination limits, but nothing essential to invoking it correctly is missing.

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%, so baseline is 3; the description adds mild value by mapping queryable dimensions (text, location, Superhost status, listing/review counts) onto parameters and implying ranking via those counts. It does not explain the interest/verification facet coupling or the default sort behavior, which remains schema-only.

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 ("Searches") and resource (the Airbnb hosts dataset) and enumerates the returned fields (name, location, bio, Superhost, verification, tenure, review and listing counts). It differentiates from the immediate follow-up sibling by naming datasets_airbnb_hosts_item, though it never distinguishes itself from datasets_airbnb_hosts_facets or the generic datasets_airbnb_search.

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?

"Use it to find or rank hosts by text, location, Superhost status, number of listings or reviews" gives clear selection criteria, and the follow-up clause routes the agent to datasets_airbnb_hosts_item for single-host detail. It lacks explicit when-not guidance (e.g., use the facets tool to discover valid interest/verification values) even though that sibling exists.

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.

Resources

Need Help?