Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

agoda_hotels_search

Search Agoda hotels by city name or city ID and return matching property IDs plus direct links to each hotel listing.

Instructions

Search Agoda hotels by city. Returns hotel search results for an Agoda city: the matching property ids for that city plus a direct link to each property's listing page. Callers may supply a known Agoda city id or a free-text city name; when both are supplied city_id takes precedence.

Input Schema

NameRequiredDescriptionDefault
cityNoFree-text city name, resolved to a numeric city id via Agoda's own destination search. Ignored when city_id is also supplied.
pageNo1-indexed result page, defaults to 1
limitNoResults per page, defaults to 10, maximum 50
city_idNoNumeric Agoda city id, e.g. 9395 for Bangkok. Either city_id or city is required; city_id takes precedence when both are supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden. It does disclose the return shape (property ids plus listing links) and the city-resolution/precedence behavior, which is genuine added context. It says nothing about authorization needs, rate limits, or pagination depth, so it is adequate but incomplete.

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?

Three tight sentences with the core purpose front-loaded and no filler. The final clause restating the city_id precedence rule duplicates the schema verbatim, a minor redundancy.

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?

For a simple 4-parameter read tool with no annotations and no output schema, the description covers purpose, inputs, precedence, and return contents. The remaining gap is that it never states that at least one of city/city_id must be supplied, which the schema asserts but the description frames as optional.

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 the schema already documents all four parameters, including the city_id-over-city precedence rule that the description repeats. Baseline 3 applies since the description adds no format, example, or constraint beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search Agoda hotels by city') and even describes the payload: matching property ids plus a direct listing link per property. That is well beyond a tautology. It does not explicitly distinguish itself from siblings like agoda_homes_search or agoda_hotel_detail, so it stops short of a 5.

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 description gives useful selection logic between two input modes ('city_id takes precedence' when both are supplied), which is implied usage guidance. However, it never says when to call this tool instead of agoda_home_search, agoda_hotel_detail, or the generic hotels_search family, and offers no when-not-to-use exclusions.

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

Deploy Server

Other Tools