List public stay-type and travel-theme pages from Vrbo's vacation-rental index to discover editorial browse categories. Returns linked travel pages, not complete search-filter results.
List Vrbo travel pages. Lists the public stay-type and travel-theme pages linked from Vrbo's vacation-rental index. These are editorial browse pages, not a complete search-filter enumeration.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does 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 that output is a curated editorial subset rather than an exhaustive list, but says nothing about pagination, auth, ordering, or return shape for a zero-param browse endpoint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight sentences, front-loaded with the verb, and the clarifying scope note comes last where it belongs. Minor redundancy in repeating 'List Vrbo travel pages / Lists the public...' but nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-param, no-output-schema browse endpoint the description covers what it returns conceptually and its non-exhaustive nature. It could say more about the fields returned, but the essentials an agent needs to pick this tool are present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify beyond what the empty schema already conveys.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (Vrbo travel pages), then defines them concretely as 'the public stay-type and travel-theme pages linked from Vrbo's vacation-rental index.' It implicitly separates the tool from vrbo_search by noting these are editorial browse pages rather than search-filter results, though it never names the sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a clear when-not signal: 'not a complete search-filter enumeration,' steering the agent away from treating this as a full catalog. It stops short of naming vrbo_search as the alternative for complete enumeration, so routing is inferable rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.