Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

expedia_properties_search

Search Expedia Stays hotels by destination and dates, returning normalized results with IDs and names. Promotional banners and sponsored slots are removed for clean property data.

Instructions

Search Expedia Stays properties. Returns normalized 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

TableJSON 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

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses a key behavior: promotional banners and sponsored ad slots are dropped, ensuring every returned property has an id and name. However, it does not mention pagination, sorting, or handling of missing data, which are relevant for a search tool.

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?

The description is two sentences with no wasted words. The primary purpose is front-loaded, and the secondary sentence adds a useful behavioral detail. It is appropriately concise and structured.

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?

For a search tool with no output schema, the description provides a basic return format (normalized results with id and name) but lacks details on pagination, result ordering, or how optional parameters like locale and currency affect output. Given the tool's complexity and the presence of sibling tools for detail/filters, this is adequate but not complete.

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 coverage is 100%, so the schema already documents all parameters. The description adds minimal semantic value beyond confirming that destination and date range are key inputs. It does not explain optional parameters like page, rooms, adults, locale, currency, or page_size, leaving their meaning to the schema types.

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 clearly states a specific verb ('Search') and resource ('Expedia Stays properties'), and clarifies the output: normalized hotel search results for a free-text destination and date range. It also distinguishes itself from sibling tools by specifying it's for properties, not flights or activities.

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

Usage Guidelines3/5

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

The description implies usage context (searching for hotel properties) but does not explicitly state when to use this tool versus alternatives like expedia_flights_search or expedia_activities_search. No exclusions or alternative guidance is provided, leaving the agent to infer from sibling names.

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