Travel Planner MCP Server

search_hotels

Find real hotel accommodations with nightly prices, ratings, and booking links. Filter by budget, star class, free cancellation, or vacation rentals.

Instructions

Search real hotel/accommodation options from Google Hotels (via SerpApi). Use this for hotel inventory, nightly/total prices, ratings, hotel class, amenities, coordinates, and booking links. Only recommend hotels returned by this tool; do not invent hotels.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "destination": "<destination>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "search_hotels"
  }
}

Input Schema

Name	Required	Description	Default
`destination`	Yes	Free-text destination: city, region, neighborhood, or property name
`check_in`	Yes	YYYY-MM-DD
`check_out`	Yes	YYYY-MM-DD
`guests`	No
`budget`	No
`constraints`	No
`currency`	No		BRL
`market`	No	Country code (Google `gl`), e.g. BR, US	BR
`locale`	No	Language code (Google `hl`), e.g. pt-BR, en	pt-BR
`result_limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 13, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations exist, so description must carry full burden. Mentions real options and source, but omits behavioral details like rate limits, data freshness, or that results are from a third-party API. Insufficient for a tool with no annotation coverage.

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?

Two sentences, each with clear purpose: first states what the tool does and its source, second provides usage constraint. No wasted words, front-loaded with critical info.

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?

Tool has 10 parameters, no output schema, and no annotations. Description lists available data types but does not cover output format, pagination, default sorting, or error handling. For a complex search tool, this is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, but description adds no parameter-specific meaning beyond 'hotel inventory, prices, ratings'. It does not elaborate on how parameters like budget, constraints, or result_limit affect the search. The description's value for parameters is minimal.

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?

Specific verb 'search' with resource 'real hotel/accommodation options from Google Hotels via SerpApi'. Clearly distinguishes from sibling 'search_flights'.

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?

Explicitly instructs to use for hotel inventory and to only recommend results from this tool, providing clear usage context. Does not mention alternatives or when not to use, but sibling tool implies domain separation.

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

Deploy Server