Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

expedia_activities_search

Search Expedia activities and tours by destination and date range to compare prices, durations, and reviews, helping you find things to do for a trip.

Instructions

Search Expedia activities. Searches Expedia things to do (activities and tours) for a free-text destination between start_date and end_date (YYYY-MM-DD), all required in the JSON body. Optional page, page_size (1-50, default 20), currency (default USD) and locale (default en_US). Each activity has its id, name, duration, price, review score and label, review count, free-cancellation flag and thumbnail.

Input Schema

NameRequiredDescriptionDefault
optionYesActivity 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"
+  },
+  "destination": {
+    "type": "string"
+  },
+  "end_date": {
+    "type": "string"
+  },
+  "locale": {
+    "type": "string"
+  },
+  "page": {
+    "type": "integer"
+  },
+  "page_size": {
+    "type": "integer"
+  },
+  "start_date": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / option / required
      Added value: +[
+  "destination",
+  "end_date",
+  "start_date"
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses required vs optional fields, defaults (page_size 20, currency USD, locale en_US), a page_size range (1-50), the date format, and the shape of each returned activity. It stops short of covering auth requirements, rate limits, or pagination totals, so it is not exhaustive.

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?

Front-loaded with the core action, then inputs, then outputs, in three tight sentences with no redundancy. Every clause (dates, defaults, return fields) earns its place.

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-payload search tool with no output schema and no annotations, the description covers inputs and enumerates return fields, which is enough to call it correctly. Minor gaps remain around pagination totals and result limits, but nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema's nested properties carry only types with no per-field descriptions, so the description does the heavy lifting: it explains `destination` as free-text, pins the date format to YYYY-MM-DD, clarifies that all three are required in the JSON body, and gives ranges/defaults for page_size, currency, and locale. This adds substantial meaning beyond the schema.

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?

Specific verb + resource: 'Search Expedia activities' and 'Searches Expedia things to do (activities and tours)'. This clearly distinguishes it from siblings like expedia_properties_search, expedia_flights_search, and expedia_locations_search without needing to open the schema.

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 (search activities by destination and date range), which is enough for an agent to infer the trigger. However, it never states when to prefer this over sibling activity search tools (e.g. agoda_activities_search, booking_attractions_search) and offers no exclusions, so guidance remains implied rather than explicit.

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