Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hotels_search

Search Hotels.com stays by destination or region ID and return date-bound results with live per-night prices, review scores, amenities, and promotional badges for chosen dates.

Instructions

Search Hotels.com hotels. Returns a page of date-bound Hotels.com hotel search results for either a free-text destination or a numeric Hotels.com region_id: property cards with per-night and per-stay prices, review score and count, location, thumbnail, amenities, and promotional badges. Provide exactly one of query or region_id; region_id skips destination typeahead resolution. Prices are the live rates Hotels.com shows for the requested check-in and check-out dates.

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": {
      "request": "<request>"
    },
    "name": "hotels_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesSearch request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / request / properties
      Added value: +{
+  "adults": {
+    "type": "integer"
+  },
+  "check_in": {
+    "type": "string"
+  },
+  "check_out": {
+    "type": "string"
+  },
+  "currency": {
+    "type": "string"
+  },
+  "locale": {
+    "type": "string"
+  },
+  "page": {
+    "type": "integer"
+  },
+  "page_size": {
+    "type": "integer"
+  },
+  "query": {
+    "type": "string"
+  },
+  "region_id": {
+    "type": "string"
+  },
+  "rooms": {
+    "type": "integer"
+  }
+}
    • addedInput schema / properties / request / required
      Added value: +[
+  "check_in",
+  "check_out"
+]
  2. Addedv1.16.2

TDQS

A4.1/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 does well: it discloses that results are paginated ("a page"), enumerates the returned fields, and clarifies that prices are live Hotels.com rates bound to the requested check-in/check-out dates. It omits auth/rate-limit/error behavior, which keeps it out of 5 territory.

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 sentences, front-loaded with the core action, then return shape, then the invocation constraint. Every sentence supplies information an agent needs before calling, with no filler or restatement of the name.

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?

With no output schema and no annotations, the description compensates well by describing the result payload and the date-bound pricing. Remaining gaps are minor: no guidance on pagination defaults or how page/page_size interact, and no note on locale/currency effects.

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 reported at 100%, so the baseline would be 3; the description adds genuine semantics on top by explaining that query is free-text vs region_id as a numeric region identifier, that the two are mutually exclusive, and that check_in/check_out determine the quoted rates. It says nothing about page, page_size, rooms, adults, locale, or currency, so not a 5.

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+resource ("Search Hotels.com hotels") and goes further by enumerating what a result contains (property cards, per-night and per-stay prices, review score, amenities). It does not distinguish itself from relevant siblings such as hotels_rates, hotels_property, or hotels_offers, so it falls just 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 Guidelines4/5

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

Gives an explicit invocation rule — "Provide exactly one of query or region_id" — and explains the consequence of each path (region_id skips typeahead resolution), which implies the autocomplete route for free-text. It never names an alternative sibling tool or states when this search should be preferred over hotels_rates/hotels_property, so it is clear context without exclusions.

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