Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

expedia_flights_search

Search Expedia flights between specific airports and dates. Compare prices, durations, and routes for one-way or round-trip travel.

Instructions

Search Expedia flights. Searches Expedia flights between two IATA airport codes, origin and destination, on departure_date (YYYY-MM-DD). return_date is required for the default round_trip; one_way is the alternative trip_type. Optional adults (1-9, default 1), cabin_class (default COACH), currency and locale. Returns departing-leg offers only, with airline, times, duration, stops, route and price.

Input Schema

NameRequiredDescriptionDefault
optionYesFlights 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"
+  },
+  "cabin_class": {
+    "type": "string"
+  },
+  "currency": {
+    "type": "string"
+  },
+  "departure_date": {
+    "type": "string"
+  },
+  "destination": {
+    "type": "string"
+  },
+  "locale": {
+    "type": "string"
+  },
+  "origin": {
+    "type": "string"
+  },
+  "return_date": {
+    "type": "string"
+  },
+  "trip_type": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / option / required
      Added value: +[
+  "departure_date",
+  "destination",
+  "origin"
+]
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations the description must carry the behavioral burden, and it does disclose the important limitation that only departing-leg offers are returned plus the defaults (adults=1, cabin_class=COACH). However it says nothing about authentication, rate limits, pagination, or currency/locale behavior, leaving meaningful gaps.

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?

Four tight sentences, front-loaded with purpose followed by parameters then return contents. Dense but no filler; every sentence carries information.

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 nested single-param tool with no output schema and no annotations, the description covers required fields, defaults, formats, and the shape of the response well enough to call it correctly. It does not explain the required 'option' wrapper object, a minor omission.

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?

The schema leaves all nested 'option' fields undocumented, and the description compensates with real detail: IATA-code semantics, YYYY-MM-DD date format, conditional return_date requirement, adults 1-9 with default 1, and cabin_class default COACH. It adds value beyond the structured fields, though currency and locale are only named, not explained.

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 flights') and precisely scopes it (between two IATA codes on a departure_date). This clearly separates it from the many expedia_properties_*/expedia_activities_* siblings, but it never names or contrasts those siblings explicitly, keeping it short of a 5.

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?

Gives in-tool usage guidance ('return_date is required for the default round_trip; one_way is the alternative trip_type'), which tells the agent how to invoke it but not when to prefer it over alternatives. No tool-selection guidance or exclusions are offered.

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