Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

Google Hotels Prices Scraper

get_google_hotel_prices

Fetch Google Hotels prices from Booking.com, Expedia, Hotels.com, Agoda, and official sites for exact dates by city or specific hotel. Use for rate shopping and rate-parity checks.

Instructions

Get Google Hotels prices from every seller (Booking.com, Expedia, Hotels.com, Agoda, the official site and more) for exact dates, by city search or specific hotels. Good for rate shopping and rate-parity checks. Priced per hotel-date. Runs the Apify actor zrk1212/google-hotels-prices-scraper on your Apify account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_google_hotel_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
adultsNoNumber of adults (default 2).
queriesNoGoogle Hotels searches, e.g. ['hotels in Austin'].
currencyNoCurrency code (default USD).
maxItemsNoMost result rows to return in this response (default 50). The run may produce more; page with get_run_results.
waitSecsNoSeconds to wait for the run to finish (default 120). If it is still running, use get_run_results later.
maxHotelsNoHotels per search query (default 3).
extraInputNoAny other input field of the Apify actor zrk1212/google-hotels-prices-scraper, passed through as-is. See https://apify.com/zrk1212/google-hotels-prices-scraper/input-schema
checkInDateNoCheck-in date YYYY-MM-DD (default: daysAhead from today).
checkOutDateNoCheck-out date YYYY-MM-DD.
maxChargeUsdNoHard spending cap for this run in USD (default 1). Apify stops charging when it is reached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-idempotent operation, so the description's added value is the commercial behavior: pricing is per hotel-date, spend runs on the user's own Apify account, and it executes the named third-party actor zrk1212/google-hotels-prices-scraper. That is meaningful context an agent cannot infer from the annotations, though it says nothing about latency or what a run returns.

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?

Three sentences, front-loaded with the resource and scope, then use cases, then billing and execution facts. No filler or restatement of the name.

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 10-parameter, cost-incurring scraper with no output schema, the definition covers purpose, scope, cost model, and the underlying actor. It stops short of describing the shape of returned rows or the run-then-poll behavior, so an agent must read the schema to learn about waitSecs and paging via get_run_results.

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 every one of the ten parameters is already documented. The description only reinforces intent ('for exact dates, by city search or specific hotels'), which loosely maps to checkInDate/checkOutDate versus queries, but adds no format or syntax detail beyond the schema.

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 and resource (get Google Hotels prices) plus the scope that matters: every seller, exact dates, and two input modes (city search or specific hotels). An agent can tell exactly what data this yields without opening the schema, and no sibling in the catalog competes for the same job.

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?

It names two use cases (rate shopping, rate-parity checks), which implies when to reach for it, but gives no exclusions, prerequisites, or explicit alternatives. The schema's mention of get_run_results for paging is never echoed in the description, so an agent gets only implied guidance about the asynchronous path.

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