Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

expedia_properties_search

Search Expedia Stays properties by destination and date range, returning clean hotel results with IDs and names while filtering out promotions and sponsored ads.

Instructions

Search Expedia Stays properties. Returns Expedia Stays (hotel) search results for a free-text destination and date range. Promotional banners and sponsored ad slots are dropped, so every returned property has an id and name.

Input Schema

NameRequiredDescriptionDefault
optionYesProperty search payload

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful non-obvious trait: promo banners and sponsored slots are stripped, so every result has an id and name. It says nothing about pagination behavior (page/page_size exist), auth needs, or how locale/currency affect results.

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?

Three tight sentences with the purpose front-loaded and no filler. The dropped-banner detail is placed after the core statement, which is the right ordering.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations and no output schema mean the description should work harder. It covers purpose and one behavioral quirk but omits pagination guidance and the semantics of rooms/adults/locale/currency, which an agent must guess at for a nested 9-field payload.

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?

Top-level schema coverage reads 100%, but the nested fields (page, page_size, rooms, adults, locale, currency) have no descriptions at all. The description adds meaning only for destination/check_in/check_out via the 'free-text destination and date range' phrasing, leaving most sub-parameters unexplained anywhere, so it lands at the baseline rather than above it.

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 Expedia Stays properties') and clarifies the output is hotel search results scoped to a free-text destination and date range. This separates it from expedia_flights_search and expedia_activities_search by resource, but it never distinguishes it from expedia_properties_detail or expedia_properties_filters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The only usage cue is 'for a free-text destination and date range,' which reads as a parameter note rather than routing guidance. No when-to-use, when-not-to-use, or alternative sibling (e.g. properties_detail for a known id) is named.

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