Crawlora MCP

vrbo_properties_reviews

Read-only

Fetch one page of public traveler reviews and aggregate review counts for a known Vrbo property. Use vrbo_search to discover rentals or vrbo_property for a property's public details.

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": {
      "property_id": "<property_id>"
    },
    "name": "vrbo_properties_reviews"
  }
}

Input Schema

Name	Required	Description
`size`	No	Page size from 1 to 50
`sort_by`	No	Sort value from the response's sort_options. Documented values: HIGHEST_TO_LOWEST_RATED, LOWEST_TO_HIGHEST_RATED, NEWEST_TO_OLDEST, NEWEST_TO_OLDEST_BY_LANGUAGE, NEWEST_TO_OLDEST_BY_RELEVANCY.
`property_id`	Yes	Vrbo property ID (optionally ending in ha)
`start_index`	No	Zero-based review offset
`include_recent_reviews`	No	Include recent reviews
`include_ratings_only_reviews`	No	Include rating-only reviews

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 7, 2026

addedInput schema / properties / include_ratings_only_reviews / description
```
Added value: +"Include rating-only reviews"
```
addedInput schema / properties / include_recent_reviews / description
```
Added value: +"Include recent reviews"
```

addedInput schema / properties / property_id / description

Added value: +"Vrbo property ID (optionally ending in ha)"

addedInput schema / properties / size / description
```
Added value: +"Page size from 1 to 50"
```

addedInput schema / properties / sort_by / description

Added value: +"Sort value from the response's sort_options. Documented values: HIGHEST_TO_LOWEST_RATED, LOWEST_TO_HIGHEST_RATED, NEWEST_TO_OLDEST, NEWEST_TO_OLDEST_BY_LANGUAGE, NEWEST_TO_OLDEST_BY_RELEVANCY."

addedInput schema / properties / start_index / description
```
Added value: +"Zero-based review offset"
```

First observedOct 5, 2026

TDQS

A4/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 usefully adds that results are paginated ("one page") and that aggregate counts are returned alongside individual reviews, but it says nothing about pagination limits, rate behavior, or auth needs.

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?

Two sentences with zero filler; the core capability is front-loaded and the sibling routing follows immediately. Every clause earns its place.

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?

An output schema exists, so return details needn't be spelled out, and annotations carry the read-only/open-world profile. What remains is that the description never states the required property_id as a precondition, a small but genuine gap for a tool keyed on a known property.

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 all six parameters are already documented in the schema. The description's "one page" phrasing gives indirect context for start_index/size but adds no syntax, defaults, or format beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (fetch) and resource (public traveler reviews plus aggregate review counts), and scopes it to "one page" for a "known Vrbo property." This lets an agent distinguish it from vrbo_search (discovery) and vrbo_property (public details) without opening either schema.

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?

Explicitly routes the agent to vrbo_search for discovering rentals and vrbo_property for property details, which is clear conditional guidance. It stops short of stating the positive trigger (you already have a property_id) as an explicit when-to-use clause, so it is clear context rather than full when/when-not coverage.

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

All Crawlora MCP tools Inspect

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

Need Help?