Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

agoda_homes_search

Search Agoda Homes and Apartments by city name or Agoda city ID, returning full details for matching apartment listings. Supply either city or city_id to get filtered homes results.

Instructions

Search Agoda Homes & Apartments by city. Returns Homes & Apartments results for an Agoda city: full listing detail for every matching property whose accommodation type is Apartment. 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 over the underlying city search, defaults to 1
limitNoCandidate listings fetched per page before filtering to homes/apartments, 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

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full behavioral burden. It does disclose the result shape (full listing detail for every matching Apartment-type property) and the city_id precedence rule, but says nothing about permissions, rate limits, or pagination behavior.

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 sentences, front-loaded with purpose and result content before the precedence rule. Slightly more verbose than necessary but every sentence carries useful information.

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

Completeness3/5

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

With no output schema and no annotations, the description must cover more ground; it does explain the returned detail and filtering, but omits usage alternatives and pagination behavior. Adequate but with visible gaps for a 4-parameter 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?

Schema description coverage is 100%, so the baseline is 3. The description restates the city_id-over-city precedence rule already documented in the schema, adding no format or semantic detail beyond what the schema provides.

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 clear verb (Search) and resource (Agoda Homes & Apartments), scoped by city, and clarifies the filter to properties whose accommodation type is Apartment. It is distinguishable from the agoda_hotels_search sibling by resource, though it never names that alternative explicitly.

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 implies usage (find homes/apartments in a city) but gives no explicit when-to-use guidance and never contrasts itself with agoda_hotels_search or agoda_hotel_detail. Usage must be inferred from the resource name.

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