Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hotels_rates

Get date-bound rates and availability for a specific Hotels.com property. Input property ID and check-in/out dates to receive per-night and per-stay prices.

Instructions

Get Hotels.com rates for one property. Returns one Hotels.com property's date-bound rates and availability: the same normalized property card Search returns, with the live per-night and per-stay prices Hotels.com shows for the requested dates. property_id is the numeric global property id from a Search response's properties[].id; it is distinct from the legacy /ho/ URL id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesRates 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.4/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 behavioral burden. It discloses that prices are live, date-bound, and normalized as in Search, and clarifies the property_id source and its distinction from the legacy URL id. It omits error/not-found behavior, but for a read-style rates endpoint this is strong disclosure.

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, all substantive, with the core action and scope front-loaded. The property_id clarification and live-price detail each earn their place without redundancy.

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 single-property rates tool with no output schema, the description covers the essential invocation path: source property_id from Search, provide dates, receive live per-night and per-stay prices. It doesn't discuss error handling or currency/locale defaults, but the schema provides structure and the description is sufficient for correct selection and calling.

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 high, so the baseline is 3, but the description adds crucial semantics for property_id: it must come from Search's properties[].id and is not the legacy URL id. This is exactly the kind of parameter knowledge that prevents incorrect calls. Other parameters (adults, locale, currency) are self-explanatory enough from their 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?

The description opens with a specific verb and resource: 'Get Hotels.com rates for one property.' It clearly states the output (date-bound rates and availability, normalized property card) and even distinguishes property_id from the legacy /ho<id>/ URL id, which sets it apart from related hotel tools.

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 clearly conveys when to use this tool: after a Search, given a property_id, when date-bound rates and availability are needed for a single property. It doesn't explicitly name alternative tools or when-not-to-use conditions, but the context is unambiguous.

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