MAQAMI Travel

getPriceIndexHotels

Read-onlyIdempotent

Retrieve historical price index data for hotels to analyze per-night pricing trends by calendar day. Supports up to 50 hotels and date range filtering.

Instructions

Overview

Retrieve historical price index data for a list of hotels. Returns average per-night prices aggregated by calendar day, allowing you to analyze pricing trends and patterns.

⚠️ Beta Feature: This endpoint is currently in beta. The API structure and behavior may change in future versions.

Pricing: $0.05 per request

Rate Limiting: This endpoint is rate-limited to 10 requests per minute for both sandbox and production API keys. Exceeding this limit will result in a 429 Too Many Requests response.

When to Use

Price trend analysis - Analyze how hotel prices change over time
Price forecasting - Use historical data to predict future pricing
Market research - Compare pricing across multiple hotels
Pricing dashboards - Build visualizations of hotel price trends

What You Get

Per-night prices - Average price per night for each calendar day
Daily aggregation - One entry per day with aggregated pricing data
Multiple hotels - Query up to 50 hotels in a single request
Future dates only - Only returns data for future check-in dates (defaults to today onwards)

Key Features

Per-night pricing - Prices are normalized to per-night rates regardless of stay duration
Daily aggregation - Each day has a single entry with the average per-night price across all stays that include that day
Future-focused - Only queries check-in dates in the future by default
Flexible date ranges - Optional date filtering with sensible defaults
Hotel limit - Maximum 50 hotel IDs per request

Parameters

hotelIds (required): Comma-separated list of hotel IDs. Maximum 50 hotel IDs allowed.
fromDate (optional): Start date in YYYY-MM-DD format. Defaults to today.
toDate (optional): End date in YYYY-MM-DD format. Defaults to 1 year from today.

Input Schema

TableJSON Schema

Name	Required	Description
`toDate`	No	End date for the price index query in YYYY-MM-DD format. Defaults to 1 year from today if not provided.
`fromDate`	No	Start date for the price index query in YYYY-MM-DD format. Defaults to today if not provided. Only future check-in dates are queried.
`hotelIds`	Yes	Comma-separated list of hotel IDs to query price index data for. Maximum 50 hotel IDs allowed per request.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: beta instability warning, $0.05 per-request pricing, a 10 req/min rate limit with the exact 429 failure mode, and the 50-hotel cap. This is exactly the behavioral detail annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with an overview and clearly sectioned, but there is real duplication: 'per-night prices,' 'daily aggregation,' and 'multiple hotels' appear in both 'What You Get' and 'Key Features,' and multiple hotels is repeated again under parameters. Trimming the redundant sections would improve density.

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

Completeness5/5

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

No output schema exists, so the description has to explain return values, and it does via 'What You Get' (per-night price per calendar day, one entry per day, aggregated). Combined with rate limits, beta status, and defaults, an agent has everything needed to call and interpret this correctly.

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%, so all three parameters are already documented in the schema. The description restates them with the same detail (YYYY-MM-DD, defaults, 50-hotel max) and adds only the 'future check-in dates only' nuance, which is already in the schema. Baseline 3 is appropriate here.

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: 'Retrieve historical price index data for a list of hotels,' and immediately scopes it to per-night averages aggregated by calendar day. This is clearly distinct from the sibling getPriceIndexCity by being hotel-list scoped rather than city scoped.

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 'When to Use' bullets describe scenarios (trend analysis, forecasting, market research) rather than conditions that select this tool over an alternative. It never points to getPriceIndexCity as the city-level counterpart, leaving the agent to infer routing.

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

Deploy Server