Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vrbo_travel_page_detail

Read-only

Get public editorial sections, rental cards, and related travel-page links for one Vrbo /travel/{slug} page. Use a slug returned by vrbo_travel_pages. Date-scoped prices are omitted; page slugs do not define search filters.

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": {
      "slug": "<slug>"
    },
    "name": "vrbo_travel_page_detail"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Vrbo travel-page slug returned by /vrbo/travel-pages"
  2. First observed

TDQS

A4.2/5.0
Behavior4/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 adds genuinely useful behavioral context beyond that: content is 'public editorial' and 'date-scoped prices are omitted', telling the agent what it will and won't receive.

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, front-loaded with the resource scope and followed by the prerequisite and a caveat. No filler; every clause adds constraining information.

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 structure needn't be described, and the description covers scope, prerequisite, and the price-omission caveat. Adequate for a single-parameter detail tool, though it could note related content limits or pagination if any.

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 single slug parameter is already documented as 'returned by /vrbo/travel-pages'. The description largely restates that source, and the added note that slugs don't define search filters is marginal for parameter semantics, so 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 ('Get') and resource ('public editorial sections, rental cards, and related travel-page links') scoped to one Vrbo /travel/{slug} page. An agent can distinguish this detail tool from the vrbo_travel_pages listing tool 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 says the slug must come from vrbo_travel_pages, establishing the prerequisite and the correct sibling to call first. It also clarifies that page slugs don't define search filters, implying this isn't a search/substitution tool, but it doesn't name a concrete 'use X instead' alternative for filtering by date.

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

All Crawlora MCP toolsInspect
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