Skip to main content
Glama
Darshan972

Scrapingdog MCP Server

by Darshan972

Google Hotels API

google_hotels

Get hotel and vacation-rental prices, ratings, and availability for any destination and date, with filters for price, rating, and more.

Instructions

Get hotel and vacation-rental prices, ratings and availability from Google Hotels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoReturn raw HTML instead of parsed JSON. (API default: false)
queryYesHotel search query (e.g. 'hotels in Paris').
adultsNoNumber of adults. (API default: 2)
ratingNoMin rating: 7=3.5+, 8=4.0+, 9=4.5+.
countryNoTwo-letter ISO country code to geo-target results (e.g. us, gb, in, de). (API default: us)
sort_byNoSort: 3=lowest price, 8=highest rating, 13=most reviews.
childrenNoNumber of children. (API default: 0)
currencyNoPricing currency. (API default: USD)
languageNoResult language code (e.g. en, es, fr, de). (API default: en)
max_priceNoMaximum price filter.
min_priceNoMinimum price filter.
hotel_classNoStar class filter (2-5), comma-separated.
check_in_dateYesCheck-in date, YYYY-MM-DD.
children_agesNoComma-separated child ages 1-17 (e.g. '5,8,10').
check_out_dateYesCheck-out date, YYYY-MM-DD.
property_tokenNoToken for detailed property information.
next_page_tokenNoPagination token from a previous response.
vacation_rentalsNoSearch vacation rentals instead of hotels. (API default: false)
free_cancellationNoOnly show free-cancellation options.
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure, but it only mentions the data returned (prices, ratings, availability). It does not address pagination tokens, output format, rate limits, or any side effects, leaving significant behavioral gaps.

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?

The description is a single, front-loaded sentence that directly captures the core function without waste. It is concise and well-structured, with every word contributing to the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (19 parameters) and lack of an output schema, the description is notably incomplete. It does not explain how to use next_page_token for pagination, what property_token does, or what the response structure looks like, making it difficult for an agent to fully understand the tool's behavior.

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?

The input schema provides 100% parameter coverage with detailed descriptions for each of the 19 parameters, so the description does not need to add additional semantics. The description adds no parameter-specific explanation beyond the schema, landing at the baseline of 3.

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?

The description uses a specific verb 'Get' and clearly identifies the resource: hotel and vacation-rental prices, ratings, and availability from Google Hotels. This distinguishes it from sibling tools like google_maps or google_shopping, making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as google_maps or google_shopping, nor are any prerequisites or exclusions mentioned. The description simply states what the tool does, leaving the agent without direction for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Darshan972/Scrapingdog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server