Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vrbo_property

Fetch public Vrbo rental details by property ID, including amenities, photos, FAQs, content sections, and aggregate rating for traveler research and comparison.

Instructions

Get Vrbo property details. Reads public traveler-facing property details, grouped amenities, photos, content sections, FAQs, and aggregate rating. Tries request profiles in order; each attempt and retry uses a fresh proxy connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
property_idYesVrbo property ID (optionally ending in ha)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/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 burden and does well: it states the data is public/traveler-facing (read-only), and discloses the retry/proxy behavior ('tries request profiles in order; each attempt and retry uses a fresh proxy connection'), which is operationally meaningful for reliability expectations. It omits failure modes and rate limiting, but covers the key behavioral traits.

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?

Three tight sentences with the purpose front-loaded, followed by return contents and then operational behavior. Every sentence carries information; no filler.

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?

No output schema exists, so the description helpfully enumerates what is returned (details, amenities, photos, content sections, FAQs, rating) plus retry behavior. For a one-parameter read tool with no annotations this is close to complete, though it could note pagination or data freshness.

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% and the single parameter is fully documented in the schema ('Vrbo property ID (optionally ending in ha)'). The description adds no syntax or format detail beyond that, 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 ('Get Vrbo property details') and enumerates the returned content (amenities, photos, content sections, FAQs, aggregate rating), which distinguishes it from review- and calendar-focused siblings. It never names a sibling explicitly, so an agent must infer the split from the content list alone.

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?

Usage is implied by the required property_id and the 'Get property details' framing, so an agent can tell this fetches one property by ID. There is no explicit when-to-use/when-not guidance and no routing to vrbo_search, vrbo_properties_reviews, or vrbo_properties_rate_calendar.

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