Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_airbnb_hosts_item

Retrieve a single Airbnb host by numeric ID from the airbnb-hosts dataset, returning the full public profile; returns 404 when the host is not yet available.

Instructions

Get an Airbnb host from the dataset. Returns one host by numeric Airbnb host id from dataset id enum value airbnb-hosts, with the full public profile: name, profile link, location, bio, Superhost, home-host and identity-verification flags, verifications, hosting and membership years, total guest reviews, number of listings and interests. Returns 404 when the host is not in the dataset yet.

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": {
      "id": "<id>"
    },
    "name": "datasets_airbnb_hosts_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Airbnb host id, e.g. 65056940

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose that the record is a 'full public profile' with its field contents plus a specific 404 failure mode for hosts not yet in the dataset. It does not cover permissions, rate limits, or data freshness, but for a public read-only lookup the disclosed behavior is solid.

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?

Two sentences, front-loaded with the verb and resource, then the return shape and the error case. The long field enumeration is dense but earns its place since no output schema exists.

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 one-parameter read tool with no output schema, the description covers identity, scope, returned fields, and the not-found case. The only gap is the unexplained 'dataset id enum value' phrasing, which is confusing given no such parameter exists.

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% and the single id parameter is documented in-schema with an example. The description reinforces that the id is a numeric Airbnb host id rather than a dataset identifier, but adds no format, range, or validity detail beyond the schema.

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 ('Get an Airbnb host') and constrains it to a single record keyed by numeric host id, which distinguishes it from the sibling search/facets tools. Minor noise: the reference to 'dataset id enum value airbnb-hosts' describes a parameter that does not exist in the schema, slightly muddling the scope.

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?

Usage is only implied: it returns exactly one host by id, so an agent can infer it is a post-search lookup, and the 404 note hints that the host may not exist. There is no explicit statement of when to prefer this over datasets_airbnb_hosts_search or the facets tools.

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