Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

klook_hot

Retrieve Klook's curated hot lists of popular destinations and activities, including Travel Must-Haves and the vertical menu, with city and activity IDs for searching or browsing.

Instructions

List Klook hot destinations and activities. Returns Klook's curated hot lists: named groups of popular destinations and popular activities, the Travel Must-Haves category group, and the short vertical menu published alongside them. Destination entries carry a city id and country name plus a landing link; use a city entry's id with /klook/search or /klook/destinations. Activity entries carry the activity id and display name. An empty hot list is a valid answer, not an error.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "klook_hot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the load, and it does well: zero-argument invocation, a detailed account of the response shape (destination entries with city id, country name, landing link; activity entries with id and display name), and the important semantic that an empty hot list is a valid answer rather than an error. It does not mention auth, rate limits, or caching, which are minor for a read-only listing.

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?

Four front-loaded sentences, no filler, with the core purpose stated before the return-shape detail. The middle sentence packing the Travel Must-Haves group and vertical menu is dense but earns its place by warning the agent the payload has multiple sections.

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

Completeness5/5

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

No output schema exists, so the description must explain returns, and it does so at entry-field granularity plus section-level structure, alongside the empty-result semantic. For a no-parameter discovery tool there is nothing an agent needs before calling it that is missing.

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

Parameters5/5

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

The tool takes zero parameters, so the baseline is 4; the description goes further by explaining the identity fields carried on each returned entry and which of them (the city id) is the usable key for downstream calls, which is the only 'parameter-like' semantics that matters here.

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?

The description names a specific verb and resource ('List Klook hot destinations and activities') and then enumerates exactly what that resource contains: curated hot lists, the Travel Must-Haves category group, and the vertical menu. Pointers to /klook/search and /klook/destinations for downstream use differentiate it from the search and catalog siblings.

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?

It makes the usage context clear (browse Klook's curated popularity lists rather than run a query) and gives concrete chaining guidance: take a destination entry's city id into /klook/search or /klook/destinations. It stops short of explicit exclusions, so an agent is not told when to prefer klook_search_hot_keywords or klook_recommendations instead.

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