Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

agoda_hotel_detail

Fetch full Agoda hotel details by property ID: name, address, rating, rooms, photo, chain, descriptions, and policies.

Instructions

Get Agoda hotel detail. Returns full hotel detail from Agoda: identity (name, any former name), an accommodation type code, address (street address, postal code, city, country), guest rating, a main photo, room count, hotel chain id, a long and short description, and short-form policy statements (minimum age, adult/child definitions, extra-bed and additional-room booking policy).

Input Schema

NameRequiredDescriptionDefault
property_idYesNumeric Agoda property id, from a prior search call's property_id field or the id embedded in an Agoda hotel URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the full burden. The 'Get ... Returns' framing clearly signals a read operation, and it discloses the returned payload in unusual detail (identity, address, rating, photo, room count, chain id, descriptions, policy statements). However, it says nothing about authentication, rate limits, or scope guarantees beyond what the payload contains.

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?

Purpose is front-loaded in the first clause, followed by a single structured enumeration of return fields. It is a long sentence, but since no output schema exists the field list earns its place; only minor trimming would be possible.

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 read-only detail tool with no output schema, the description adequately substitutes by enumerating the return shape. It covers identity, address, rating, media, capacity, chain, and policy fields; the main gap is that it does not state the source/authority of the id or any prerequisite that a search must run first, which an agent calling blind could miss.

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?

With a single parameter at 100% schema description coverage, the schema already explains that property_id is a numeric Agoda property id sourced from a prior search or an Agoda URL. The description adds no further parameter meaning, so the baseline of 3 applies.

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 ('Get Agoda hotel detail') and enumerates exactly what the response contains, so the agent knows the operation. The 'Agoda' qualifier also implicitly distinguishes it from siblings like booking_hotel_detail, tripcom_hotel_detail, and expedia_properties_detail, though it never names or contrasts those siblings directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description contains no when-to-use, when-not-to-use, or alternative-tool guidance at all. The only workflow hint ('from a prior search call's property_id field or the id embedded in an Agoda hotel URL') lives in the schema, not the description, so routing decisions are left entirely to inference.

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