Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

expedia_properties_detail

Fetch Expedia hotel details by property ID and stay dates. Get name, star rating, address, amenities, and VIP message for trip planning.

Instructions

Expedia Stays property detail. Returns a summary for one Expedia hotel by property_id, for the stay given by check_in and check_out (YYYY-MM-DD), all required in the JSON body. Optional adults (1-9, default 2), currency and locale. The response has the name, star rating, address, city, province, country code, coordinates, top amenities and VIP message.

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": {
      "option": "<option>"
    },
    "name": "expedia_properties_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionYesProperty detail 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"
      +  },
      +  "locale": {
      +    "type": "string"
      +  },
      +  "property_id": {
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / option / required
      Added value: +[
      +  "check_in",
      +  "check_out",
      +  "property_id"
      +]
  2. Added

TDQS

A3.8/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 behavioral burden, and it does substantial work: it declares the request body shape ('all required in the JSON body'), the date format, the `adults` range and default, and enumerates the response contents. What is missing is any auth/rate-limit note, but for a read-only detail lookup this is reasonably complete.

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, front-loaded with purpose, then inputs, then response shape. Dense but every clause contributes; no filler.

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?

With a nested `option` object, no annotations, and no output schema, the description compensates well by documenting both the input contract and the returned fields. Only the absence of any authentication or error-behavior note keeps it from being fully complete.

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 description coverage is 100%, so baseline is 3, but the description exceeds it by adding constraints the flat schema lacks: `YYYY-MM-DD` date format, `adults` range 1-9 with default 2, and the optional status of `currency`/`locale`.

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 and resource: 'Returns a summary for one Expedia hotel by `property_id`' scoped to a date range. It is readily distinguishable from the search/reviews siblings by the 'one hotel' framing, though it never names an alternative tool.

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?

Usage is implied: use this when you already have a `property_id` and stay dates. There is no explicit 'when not to use' guidance and no routing to `expedia_properties_search` for discovery or `expedia_properties_reviews` for reviews, so the agent must infer the workflow.

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