Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vrbo_properties_reviews

Fetch Vrbo property reviews by property ID, returning paginated public traveler feedback, aggregate counts, and available sort choices 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.

Input 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.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose that it returns one page of public traveler reviews, an aggregate count, and sort choices. It does not explicitly state read-only behavior, permissions, rate limits, or error behavior, so it is adequate but not rich.

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?

The description is three short sentences and is front-loaded with the core purpose. Every sentence contributes useful context about return scope or pagination/sort behavior.

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?

There is no output schema, so the description appropriately notes that it returns one page of reviews plus an aggregate count and sort choices. It is complete enough for an agent to select and call the tool, though it could say more about the review objects themselves.

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 parameters are already well documented. The description adds only that pagination and sort values follow the public reviews query, which does not go much beyond the schema.

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?

The description gives a specific verb and resource: it gets Vrbo property reviews. It is clear what the tool returns, but it does not explicitly distinguish itself from sibling tools such as vrbo_property or other review endpoints.

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: call this when public traveler reviews for a Vrbo property are needed. The description mentions pagination and sort behavior but gives no explicit when-to-use/when-not-to-use guidance or 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