Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vrbo_properties_reviews

Fetch a page of public Vrbo property reviews with aggregate count, sort choices, and pagination. Use a property ID to retrieve traveler feedback for analysis or display.

Instructions

Get Vrbo property reviews. Returns one page of public traveler reviews, aggregate count, and current sort choices. Pagination and sort values follow the public reviews query; each property-page and GraphQL request uses a fresh proxy connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoPage size from 1 to 50
sort_byNoSort value from the response's sort_options
property_idYesVrbo property ID (optionally ending in ha)
start_indexNoZero-based review offset
include_recent_reviewsNoInclude recent reviews
include_ratings_only_reviewsNoInclude rating-only reviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/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 behavioral burden. It usefully discloses the return shape (one page, aggregate count, sort options) and notes a fresh proxy connection per property-page/GraphQL request, which is unusual and worth stating. However, it omits auth requirements, rate limiting, and error behavior, leaving meaningful gaps for a tool with zero annotation coverage.

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?

Three compact sentences with the core purpose front-loaded and no filler. The final proxy-connection sentence is somewhat tangential but still informative, so the structure holds up well overall.

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 no output schema present, the description partially compensates by describing the return payload (one page of reviews, aggregate count, sort choices). Combined with full schema coverage and a clear required parameter, this is mostly complete, though pagination mechanics and sort-value sourcing could be spelled out more explicitly.

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 size, sort_by, property_id, start_index, and the two inclusion flags. The description adds only a light hint that sort values 'follow the public reviews query,' which lightly reinforces the enum's provenance but adds little 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?

The description opens with a specific verb and resource ('Get Vrbo property reviews') and immediately scopes the output to 'public traveler reviews, aggregate count, and current sort choices.' This makes it clearly distinct from property-detail siblings like vrbo_property or vrbo_search without the agent needing to open another schema.

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

Usage Guidelines2/5

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

The description never states when to use this tool versus the many sibling tools (vrbo_property, vrbo_search, vrbo_properties_rate_calendar). It hints that pagination and sort 'follow the public reviews query,' but gives no when-to-use, when-not-to-use, or alternative routing guidance.

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