Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vrbo_search

Search Vrbo vacation rental listings by destination, dates, rooms, filters, and sort order, returning available properties and live filter metadata for trip planning.

Instructions

Search Vrbo vacation rentals. Searches public Vrbo rental listings for a selected destination and dates. Obtain destination, region_id, and lat_long from Vrbo's destination suggestion UI. Supports date flexibility, per-room adult and child-age inputs, current filter selections and ranges, and observed sort values. Copy filter IDs and option values from the returned filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesSearch criteria

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that filters are dynamic and must be copied from a prior search response and where destination identifiers come from, but it says nothing about result structure, pagination, or limit behavior for a multi-parameter search.

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 short sentences with the core purpose front-loaded and the workflow guidance after it. There is minor redundancy between 'Search Vrbo vacation rentals' and the following sentence, but nothing that meaningfully wastes space.

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 complex nested tool with five required parameters, no annotations, and no output schema, the description supplies the key operational context: where the destination identifiers come from and how to obtain valid filter IDs. It omits any mention of return shape or result limits, which is the main remaining gap.

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 the schema already documents the nested request fields, the rooms override, child-age bounds, and filter structure. The description paraphrases these ('per-room adult and child-age inputs, current filter selections and ranges') without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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 Vrbo vacation rentals', 'Searches public Vrbo rental listings for a selected destination and dates'), so an agent can identify it as the listing-search tool. It does not explicitly name siblings like vrbo_locations_search or vrbo_property, so differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a concrete prerequisite workflow: obtain destination, region_id and lat_long from Vrbo's destination suggestion UI, and copy filter IDs and option values from returned filters. This tells the agent how to prepare a valid call, though it gives no explicit when-not-to-use guidance or named alternatives.

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