Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

klook_search

Search Klook travel activities by free-text query, destination city, category, filters, price range, and sort order; returns matching activities and listings for trip planning.

Instructions

Search Klook travel activities. Returns Klook activity search results for a free-text query, a destination city, or a category. A free-text query runs Klook keyword search against its en-US catalogue and can be combined with city_id and category_id; without a query the request browses a destination or category listing instead. Use city_id from /klook/destinations (or a city from /klook/suggest) and category_id from /klook/categories; the tag filters (interest_tag, service_lang_tag, duration_tag, other_filters_tag) take ids from /klook/search/filters, and interest_tag is browse-only. sort reorders the same result set. A query with no matches returns an empty activities list, Klook caps the reported total at 10000 for broad queries, and prices are display strings in the response currency.

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

Input Schema

Name	Required	Description
`page`	No	1-based result page
`sort`	No	Result ordering
`query`	No	Free-text activity search. At least one of query, city_id or category_id is required.
`city_id`	No	Klook city id from /klook/destinations or /klook/suggest
`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 category id from /klook/categories
`duration_tag`	No	Duration-bucket id from /klook/search/filters
`interest_tag`	No	Interest/topic id from /klook/search/filters; browse only, not with query
`service_lang_tag`	No	Guided-language id from /klook/search/filters
`other_filters_tag`	No	Service/feature id from /klook/search/filters

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4/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 discloses meaningful behavior: en-US catalogue keyword search, browse mode without a query, empty results for no matches, a reported total cap of 10000, display-string prices, and sort affecting the same result set. It does not cover authentication, rate limits, or detailed response shape, so it is strong but not exhaustive.

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?

The description is dense and front-loaded with the primary purpose, then moves into mode behavior, ID provenance, and edge cases. Most sentences earn their place, though the opening two sentences overlap slightly in restating the search action.

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 12-parameter search tool with no annotations and no output schema, the description covers the main usage modes, ID sourcing, filtering constraints, and several edge cases. It is largely complete, though it does not describe the response fields beyond noting that activities are returned and prices are display strings.

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

Parameters4/5

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

Schema coverage is already 100%, which sets a baseline of 3, but the description adds value beyond the schema. It explains where city_id and category_id come from, that tag filters use IDs from /klook/search/filters, that interest_tag cannot be combined with query, and that sort only reorders the same result set.

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?

The description states a specific verb and resource: search Klook travel activities. It clearly explains the three search modes (free-text query, destination city, category) and how they combine. It does not explicitly distinguish itself from sibling tools such as klook_search_unified or klook_attractions_search, which keeps it from 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 Guidelines4/5

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

It gives clear mode-selection guidance: free-text query versus browsing a destination or category listing. It also names where required IDs come from and explicitly says interest_tag is browse-only, which is a useful exclusion. It stops short of naming alternative sibling tools or explaining when another search tool would be preferable.

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

Deploy Server