Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hotels_offers

Get public room offer summaries for a Hotels.com property and date range, including room labels and non-transactional messages. Use property_id from Search.

Instructions

Get Hotels.com room offers. Returns the public room/unit offer summaries shown for one Hotels.com property and date range, including room labels and non-transactional offer messages. Booking, checkout, payment, and reservation tokens are never returned. property_id is the numeric global property id from a Search response.

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_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRoom offers 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"
+  },
+  "property_id": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / request / required
      Added value: +[
+  "check_in",
+  "check_out",
+  "property_id"
+]
  2. Addedv1.16.2

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden. It explicitly states public scope, what is returned (room labels and non-transactional offer messages), and what is never returned (booking/checkout/payment/reservation tokens). It omits details like pagination or error behavior, but the core behavioral boundary is well disclosed.

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 with no filler, opening with the action and resource, then the behavioral boundary and a key parameter note. Every sentence contributes.

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 read-only retrieval tool with no output schema, the description conveys what is returned, what is not returned, and the key required input. It could be more complete by documenting expected date/locale/currency formats, but an agent can correctly invoke it with the information given.

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 high, so baseline 3 applies. The description adds useful semantics for property_id (numeric global property id from a Search response), but check_in/check_out formats, adults, locale, and currency are left to inference from parameter names.

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?

States a specific verb ('Get') and resource ('Hotels.com room offers'), scoping to one property and date range. The return content boundary ('room labels and non-transactional offer messages') also helps differentiate it from sibling tools like hotels_rates and hotels_property.

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 gives clear context: use it after obtaining a property_id from a Search response to fetch public offer summaries for a property/date range. It does not explicitly name sibling alternatives or state when not to use it, so it falls short of a perfect 5.

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