Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hotels_property

Fetch Hotels.com property details from a canonical URL, returning name, address, rating, images, and amenities while excluding availability, prices, booking, and reviews.

Instructions

Get Hotels.com property details. Returns public static metadata from one canonical Hotels.com property page, including name, address, rating, images, and amenities. Date-bound availability, prices, booking, and review content are excluded.

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

Input Schema

NameRequiredDescriptionDefault
requestYesCanonical Hotels.com property URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / request / properties
      Added value: +{
+  "url": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / request / required
      Added value: +[
+  "url"
+]
  2. Addedv1.16.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden, and it does well: it labels the data as 'public static metadata,' identifies the source as one canonical property page, and lists what is and is not included. It does not disclose error behavior or response structure, but for a simple single-URL read tool this is a meaningful and honest behavioral 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?

Two tightly written sentences carry the full message: what the tool does, what it returns, and what it excludes. Every clause adds value and the core action is front-loaded.

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-parameter, no-output-schema tool, the description covers what input is needed and what the response will contain, including explicit exclusions. It could be slightly richer by mentioning how to obtain a canonical URL or what happens with an invalid one, but nothing essential is missing for a typical agent invocation.

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?

The schema already documents the only parameter (url) with the description 'Canonical Hotels.com property URL,' and the schema coverage is 100%. The tool description adds the context that this should be 'one canonical Hotels.com property page,' but it does not substantially add parameter syntax or formatting guidance beyond what the schema provides.

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 property details') and then narrows the scope by naming exact returned fields (name, address, rating, images, amenities). It also distinguishes itself from pricing/review tools by explicitly excluding availability, prices, booking, and review content.

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 communicates that this tool is for static property metadata and not for dynamic content like prices or reviews, giving an agent a solid when-to-use signal. It stops short of explicitly naming sibling alternatives such as hotels_rates or hotels_reviews, so it earns a 4 rather than a 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