Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

klook_attractions_search

Find theme parks, museums, and attraction tickets by searching Klook's catalogue with destination, category, price, and language filters; returns paginated listings with display prices.

Instructions

Search Klook attractions by destination or category. Returns one page of Klook's attractions-vertical listings (theme parks, museums, observation decks and the rest of the attraction-ticket catalogue) for an optional destination city and/or attraction category. Use city_id from /klook/destinations and category_id from /klook/attractions/categories; with neither it returns Klook's global attractions listing. Unlike /klook/search this reads Klook's dedicated attractions catalogue, which is a separate inventory from the general experiences search. sort reorders the same result set, page is 1-based, and prices are display strings in the response currency. Klook caps the reported total at 10000 for broad queries.

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_attractions_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based result page
`sort`	No	Result ordering
`city_id`	No	Klook city id from /klook/destinations; omit to browse globally
`per_page`	No	Results per page, 1-50
`price_max`	No	Maximum price in the response currency; requires price_min
`price_min`	No	Minimum price in the response currency; requires price_max
`category_id`	No	Klook attraction category id from /klook/attractions/categories
`duration_tag`	No	Duration tag id, e.g. 7959 (0-3 hours)
`service_lang_tag`	No	Guided-language tag id, e.g. 3029 (English guided)
`other_filters_tag`	No	Other-filter tag id, e.g. 3013 (Free cancellation)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and handles most of it: it discloses pagination ('one page'), that sort reorders rather than filters the same result set, that page is 1-based, that prices come back as display strings in the response currency, and that Klook caps reported totals at 10000 for broad queries. Missing only operational traits such as auth needs, rate limits, or error behavior, which keeps it short of a 5.

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?

Front-loaded with purpose before any caveats, and the sequence (what it returns → id provenance → fallback → sibling contrast → pagination/price/sort notes → total cap) is logical. The parenthetical listing attraction types is a little expansive and the closing cap note is dense, but no sentence is filler.

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?

For a 10-parameter, optional-only search tool with no annotations and no output schema, the description supplies everything an agent needs to call it correctly: inventory scope, id sources, no-arg behavior, sibling differentiation, paging semantics, and a known reporting limit. Parameter-level detail is fully delegated to a schema that covers 100% of fields, which is the right division of labor.

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 coverage is 100% and the schema already documents every parameter's source, enum, and pairing constraint, so the baseline applies. The description adds modest meaning—sort changes ordering but not the result set, page is 1-based, prices are display strings in the response currency—but adds nothing for duration_tag, service_lang_tag, or other_filters_tag beyond what the schema examples provide.

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?

States a specific verb and resource ('Search Klook attractions') plus scope (destination city and/or category) and enumerates what the catalogue contains (theme parks, museums, observation decks). It also explicitly distinguishes itself from /klook/search as a separate inventory, so an agent can tell the two apart without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit prerequisites and provenance for both filter keys (city_id from /klook/destinations, category_id from /klook/attractions/categories), states the fallback behavior when neither is supplied (global attractions listing), and names the alternative tool (/klook/search) with the condition that selects this one instead. That is when-to-use, when-not, and alternatives in one paragraph.

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

Deploy Server