Skip to main content
Glama
soren-olympus

Amadeus Hotel API MCP Server

amadeus_hotel_list

Search for hotels in a city by IATA code. Filter results by star rating, amenities, and hotel name to find suitable accommodation.

Instructions

Search for hotels in a specific city. Retrieves a list of hotels based on location and optional filters including amenities, star rating, and hotel name. This is useful for getting an overview of accommodation options in a destination. 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_list({"cityCode": "PAR"})

  • amadeus_hotel_list({"cityCode": "NYC", "ratings": [4, 5]})

  • amadeus_hotel_list({"cityCode": "LON", "amenities": ["SWIMMING_POOL", "WIFI"]})

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.
radiusNoRadius around the coordinates in KM (max 100)
radiusUnitNoRadius unit (KM only)KM
amenitiesNoFilter by amenities (e.g., SWIMMING_POOL, WIFI)
ratingsNoFilter by star ratings (1-5)
hotelNameNoFilter by hotel name
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether it is read-only, rate limits, or authentication requirements. The tool likely performs an API call, but this is not clarified.

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?

The description is concise with a clear purpose followed by examples. It is front-loaded and efficient, though slightly verbose in listing examples.

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?

With no output schema, the description should explain the return format or content. It does not mention what the response contains, such as hotel IDs or details, leaving a gap for the agent.

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 baseline is 3. The description adds examples and emphasizes valid IATA codes, adding some value, but does not provide substantial additional meaning 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?

Description clearly states the tool searches for hotels in a specific city and retrieves a list. It specifies the main filter options, distinguishing it from siblings like booking and search.

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?

The description indicates the tool is useful for getting an overview of accommodation options, providing context. However, it does not explicitly state when not to use it or list alternatives among siblings.

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