Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vrbo_search

Read-only

Search public Vrbo vacation rentals by destination and dates, with adult counts, child ages, observed sort choices, live facet selections, and nightly or total price ranges. Use Vrbo destination suggestions to obtain region_id and lat_long.

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": {
      "destination": "<destination>",
      "region_id": "<region_id>",
      "lat_long": "<lat_long>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "vrbo_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order, default RECOMMENDED; choose RECOMMENDED, PRICE_LOW_TO_HIGH, PRICE_HIGH_TO_LOW, REVIEW, or REVIEW_COUNT.
limitNoMaximum listings to return; defaults to 20 and is capped at 50.
roomsNoOne or more requested rooms with per-room adults and child_ages. Use this instead of adults and child_ages for multi-room searches.
adultsNoAdult guest count for the single-room shorthand; omitted or zero defaults to 2 and values above 16 are capped. Do not set with rooms.
filtersNoApply categorical selections from a previous Vrbo search response; copy the returned filter and option IDs and values.
check_inYesRequired arrival date in YYYY-MM-DD format.
lat_longYesRequired latitude,longitude pair from the selected vrbo_locations_search result; latitude must be -90..90 and longitude -180..180.
check_outYesRequired departure date in YYYY-MM-DD format, after check_in.
region_idYesRequired numeric Vrbo region ID from the selected vrbo_locations_search result.
child_agesNoChild ages 2–17 for the single-room shorthand. Do not combine with rooms.
destinationYesTraveler-facing destination name returned by vrbo_locations_search; provide its matching region_id and lat_long too.
flexibilityNoDate-flexibility window: 0_DAY for exact dates (default) or 3_DAY.
filter_rangesNoApply observed numeric price ranges by live range ID; captured IDs include nightly_price and total_price.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • addedInput schema / properties / adults / description
      Added value: +"Adult guest count for the single-room shorthand; omitted or zero defaults to 2 and values above 16 are capped. Do not set with rooms."
    • addedInput schema / properties / check_in / description
      Added value: +"Required arrival date in YYYY-MM-DD format."
    • addedInput schema / properties / check_out / description
      Added value: +"Required departure date in YYYY-MM-DD format, after check_in."
    • changedInput schema / properties / child_ages / description
      Previous value: -"ChildAges contains ages 2–17 for children in the default single room."New value: +"Child ages 2–17 for the single-room shorthand. Do not combine with rooms."
    • addedInput schema / properties / destination / description
      Added value: +"Traveler-facing destination name returned by vrbo_locations_search; provide its matching region_id and lat_long too."
    • changedInput schema / properties / filter_ranges / description
      Previous value: -"Ranges applies numeric ranges by their live nested facet ID."New value: +"Apply observed numeric price ranges by live range ID; captured IDs include nightly_price and total_price."
    • addedInput schema / properties / filter_ranges / items / properties / id / description
      Added value: +"Observed numeric range ID from search response metadata, such as nightly_price or total_price."
    • addedInput schema / properties / filter_ranges / items / properties / max / description
      Added value: +"Finite upper bound at least as large as min."
    • addedInput schema / properties / filter_ranges / items / properties / min / description
      Added value: +"Finite non-negative lower bound for this price range."
    • changedInput schema / properties / filters / description
      Previous value: -"Filters are selections copied from the live facet metadata in a search response."New value: +"Apply categorical selections from a previous Vrbo search response; copy the returned filter and option IDs and values."
    • addedInput schema / properties / filters / items / properties / id / description
      Added value: +"Observed filter or option ID from search response metadata; use the option ID when it differs from its parent group ID."
    • addedInput schema / properties / filters / items / properties / values / description
      Added value: +"One or more exact option values returned for this filter; provide at least one non-empty value."
    • addedInput schema / properties / flexibility / description
      Added value: +"Date-flexibility window: 0_DAY for exact dates (default) or 3_DAY."
    • addedInput schema / properties / lat_long / description
      Added value: +"Required latitude,longitude pair from the selected vrbo_locations_search result; latitude must be -90..90 and longitude -180..180."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum listings to return; defaults to 20 and is capped at 50."
    • addedInput schema / properties / region_id / description
      Added value: +"Required numeric Vrbo region ID from the selected vrbo_locations_search result."
    • changedInput schema / properties / rooms / description
      Previous value: -"Rooms overrides Adults and ChildAges and supports multi-room searches."New value: +"One or more requested rooms with per-room adults and child_ages. Use this instead of adults and child_ages for multi-room searches."
    • addedInput schema / properties / rooms / items / properties / adults / description
      Added value: +"Adult guests for this room, from 1 through 16."
    • addedInput schema / properties / rooms / items / properties / child_ages / description
      Added value: +"Ages 2–17 for children in this room."
    • changedInput schema / properties / sort / description
      Previous value: -"Documented values: RECOMMENDED, PRICE_LOW_TO_HIGH, PRICE_HIGH_TO_LOW, REVIEW, REVIEW_COUNT."New value: +"Sort order, default RECOMMENDED; choose RECOMMENDED, PRICE_LOW_TO_HIGH, PRICE_HIGH_TO_LOW, REVIEW, or REVIEW_COUNT."
  2. Changed5 schema fields changed
    • addedInput schema / properties / child_ages / description
      Added value: +"ChildAges contains ages 2–17 for children in the default single room."
    • addedInput schema / properties / filter_ranges / description
      Added value: +"Ranges applies numeric ranges by their live nested facet ID."
    • addedInput schema / properties / filters / description
      Added value: +"Filters are selections copied from the live facet metadata in a search response."
    • addedInput schema / properties / rooms / description
      Added value: +"Rooms overrides Adults and ChildAges and supports multi-room searches."
    • addedInput schema / properties / sort / description
      Added value: +"Documented values: RECOMMENDED, PRICE_LOW_TO_HIGH, PRICE_HIGH_TO_LOW, REVIEW, REVIEW_COUNT."
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context that sort choices and facet selections are 'observed' and 'live' (i.e., sourced from prior responses), but says nothing about rate limits, pagination, or result caps beyond what the schema states.

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?

Two sentences: the first front-loads the purpose and capability scope, the second gives the input-sourcing prerequisite. There is little waste, though the capability list is somewhat dense and could be trimmed.

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 an output schema present, return values need not be explained, and annotations plus full schema coverage handle safety and parameters. The description is complete enough for an agent to call correctly, missing only explicit alternative-tool routing and pagination/limit caveats.

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 description coverage is 100%, so each parameter is already documented in the schema with formats, defaults, and constraints. The description only groups the parameter families (guest counts, sort, facets, price ranges) without adding syntax or semantics beyond the schema, which is the expected baseline.

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 ('Search public Vrbo vacation rentals') and enumerates the searchable dimensions (destination, dates, guest counts, sort, facets, price ranges). An agent can tell this is the primary listing-search endpoint, though the description does not explicitly distinguish it from siblings like vrbo_properties_reviews or vrbo_property.

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?

Provides a real workflow prerequisite: obtain region_id and lat_long via Vrbo destination suggestions before calling. However, it never states when to use this tool versus alternatives (e.g., vrbo_property for a single listing, or non-Vrbo search tools), leaving the selection logic to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources