Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vrbo_travel_page_detail

Fetch a Vrbo /travel/{slug} page to retrieve public editorial sections, visible rental cards, and related travel-page links; date-scoped prices are omitted.

Instructions

Get a Vrbo travel page. Returns public editorial sections, visible rental cards, and related travel-page links for a /travel/{slug} page. Date-scoped prices are omitted; page slugs are not search-filter values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesVrbo travel-page slug returned by /vrbo/travel-pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/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 reasonably well: it discloses that only 'public editorial' content and 'visible' cards are returned and explicitly warns that date-scoped prices are omitted. It adds useful behavioral context beyond a bare read claim, though it doesn't state rate limits or how 'visible' is determined.

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 tight sentences: purpose first, return contents second, and the two caveats (no prices, slug semantics) last. Every sentence carries information and the key scope is front-loaded.

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 single-parameter read tool with no output schema, the description covers what is returned and what is deliberately excluded, which is what an agent needs to call it correctly. The absence of output schema is compensated, though pagination/limits are unaddressed.

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 coverage is 100% and the schema already documents the slug as 'returned by /vrbo/travel-pages'. The description adds only a marginal clarification ('not search-filter values'), so the schema does the heavy lifting and 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?

The description opens with a specific verb+resource ('Get a Vrbo travel page') and enumerates the returned content (editorial sections, rental cards, related travel-page links) scoped to a /travel/{slug} URL. This clearly separates it from search-oriented siblings like vrbo_search or vrbo_locations_search, though it never names the closest sibling (vrbo_travel_pages) explicitly.

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?

The note 'page slugs are not search-filter values' implies this tool is for fetching a known page, not for filtering/searching, and the schema points to /vrbo/travel-pages as the slug source. However, there is no explicit 'use this instead of X when Y' routing, so usage is only implied rather than stated.

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