Skip to main content
Glama
soren-olympus

Amadeus Hotel API MCP Server

amadeus_hotel_search

Search for hotel offers by city, dates, and guest count. Returns available rooms with pricing, board types, and cancellation policies.

Instructions

Search for hotel offers (available rooms with pricing) based on location, dates, guests, and other criteria. This tool provides detailed pricing and availability information for specific stay dates, including room types, board options, and cancellation policies. Always use valid IATA 3-letter city codes (e.g., 'PAR' for Paris, 'NYC' for New York, 'LON' for London, 'SFO' for San Francisco, 'LAX' for Los Angeles).

Examples:

  • amadeus_hotel_search({"cityCode": "PAR", "checkInDate": "2025-04-01", "checkOutDate": "2025-04-05", "adults": 2})

  • amadeus_hotel_search({"cityCode": "NYC", "checkInDate": "2025-04-10", "checkOutDate": "2025-04-15", "adults": 2, "currency": "USD"})

  • amadeus_hotel_search({"cityCode": "LON", "checkInDate": "2025-05-01", "checkOutDate": "2025-05-07", "adults": 1, "roomQuantity": 1, "priceRange": "100-300"})

  • amadeus_hotel_search({"cityCode": "SFO", "checkInDate": "2025-06-15", "checkOutDate": "2025-06-20", "hotelName": "Grand Hyatt", "boardType": "BREAKFAST"})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityCodeYesIATA city code (e.g., 'PAR' for Paris, 'NYC' for New York, 'LON' for London, 'SFO' for San Francisco, 'LAX' for Los Angeles). Must be a valid 3-letter IATA city code.
checkInDateYesCheck-in date in YYYY-MM-DD format
checkOutDateYesCheck-out date in YYYY-MM-DD format
adultsNoNumber of adult guests
roomQuantityNoNumber of rooms
priceRangeNoPrice range (e.g., '100-200' for prices between 100 and 200)
currencyNoCurrency code (e.g., USD, EUR)USD
boardTypeNoBoard type (e.g., ROOM_ONLY, BREAKFAST, HALF_BOARD, FULL_BOARD, ALL_INCLUSIVE)
includeClosedNoInclude closed properties
bestRateOnlyNoReturn only best available rate
langNoPreferred language for hotel descriptionsEN
paymentPolicyNoFilter by payment policy typeNONE
hotelNameNoFilter by hotel name
Behavior3/5

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

Description mentions the output includes pricing, room types, board options, and cancellation policies, but lacks information on pagination, rate limits, or actions if no results. Since no annotations exist, it carries the full burden, and more transparency would be beneficial.

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

Conciseness4/5

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

Description is a paragraph followed by four examples. It front-loads the purpose and is reasonably concise, though examples take space. Each sentence serves a clear function.

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?

With 13 parameters and no output schema, the description covers the main behavior (pricing and availability), lists key filters, and provides examples for typical use. It lacks details on error scenarios or output structure, but is adequate for a search tool.

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?

Input schema has 100% coverage, so baseline is 3. Description adds value through examples showing parameter usage, but does not explain parameters beyond what schema already provides. No additional semantic depth.

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 clearly states 'Search for hotel offers (available rooms with pricing)' with specific verb and resource. It distinguishes from sibling tools like amadeus_hotel_booking, amadeus_hotel_list, and amadeus_hotel_offer by focusing on search/pricing.

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?

Provides clear guidance to use valid IATA codes and shows multiple examples. However, it does not explicitly say when not to use this tool versus siblings, nor does it exclude alternative tools.

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/soren-olympus/amadeus-mcp'

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