Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

expedia_locations_search

Search Expedia destinations by free-text term to get location and property suggestions with coordinates, region IDs, property IDs, or airport codes. Supports optional currency and locale.

Instructions

Search Expedia destinations. Returns Expedia destination and property suggestions for a free-text term (required, 100 characters or fewer), with optional currency and locale. Each item has its type, geo type, primary and secondary text, full location name, coordinates, and region_id, property_id or airport_code where they exist.

Input Schema

NameRequiredDescriptionDefault
optionYesLocation search payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / option / properties
      Added value: +{
+  "currency": {
+    "type": "string"
+  },
+  "locale": {
+    "type": "string"
+  },
+  "term": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / option / required
      Added value: +[
+  "term"
+]
  2. Added

TDQS

B3.4/5.0
Behavior3/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. It usefully discloses the return structure (type, geo type, text fields, coordinates, and possible IDs) and the required term limit, but it omits operational details such as pagination, result limits, or authentication requirements.

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?

The description is three sentences and front-loads the core purpose before detailing inputs and return fields. It is efficient overall, though the return-field list is slightly dense.

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?

Given no output schema and no annotations, the description compensates by explaining the return item structure in some detail. It is nearly complete for a simple search tool, with only minor gaps around pagination or result limits.

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 high, establishing a baseline of 3, but the description adds useful meaning beyond the schema: it marks `term` as required and limited to 100 characters, and identifies `currency` and `locale` as optional refinements. This goes beyond the bare nested schema.

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?

The description states a specific verb and resource: 'Search Expedia destinations' and clarifies it returns destination and property suggestions. It is clear what the tool does, but it does not explicitly distinguish itself from nearby siblings such as expedia_properties_search or expedia_properties_detail.

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 description explains inputs and outputs but gives no guidance on when to use this tool versus alternatives. It does not say whether this is intended to resolve destination IDs before property search, nor does it mention any exclusions or prerequisites.

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