Skip to main content
Glama

klook_attractions_search

Read-only

Search the Klook attractions-ticket vertical (theme parks, water parks, museums, observation decks and similar tickets) and return one page of normalized activity cards with activity id, title, canonical URL, price display strings, rating, review count and tags, plus the destination and total. Provide at least one of city_id (from klook_destinations) or category_id (from klook_attractions_categories); sort, price_min/price_max and page/per_page refine the same result set. Use klook_search for tours and experiences instead, and klook_search_filters with vertical=attractions when you need the attraction category ids and available dates.

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

NameRequiredDescriptionDefault
pageNo1-based result page. Defaults to 1.
sortNoResult ordering. One of recommended, bestselling, top_rated, price_low_to_high, newest. Defaults to recommended.
city_idNoOptional Klook city id from /klook/destinations. Omit it (and category_id) for Klook's global attractions listing.
end_dateNoOptional latest participation date in RFC 3339 form, e.g. 2026-12-05T00:00:00Z.
per_pageNoResults per page, 1-50. Defaults to 20.
price_maxNoOptional maximum price in the response currency.
price_minNoOptional minimum price in the response currency. Must not exceed price_max.
start_dateNoOptional earliest participation date in RFC 3339 form, e.g. 2026-12-01T00:00:00Z. Must not be after end_date.
category_idNoOptional Klook attraction category id from /klook/attractions/categories.
duration_tagNoOptional duration-bucket id from /klook/search/filters (duration_tag group).
service_lang_tagNoOptional guided-language id from /klook/search/filters (service_lang_tag group).
other_filters_tagNoOptional service/feature id from /klook/search/filters (other_filters_tag group).

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds value by disclosing the exact normalized card fields returned (id, title, canonical URL, price strings, rating, review count, tags, destination, total) and the one-page pagination model. It stops short of stating rate limits, result caps, or empty-result behavior, so it earns a 4 rather than 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?

Two sentences, no filler, with the resource scope and the result shape front-loaded before the disambiguation guidance. The second sentence is dense with comma-separated lists but every clause carries routing or scoping information.

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, fully schema-documented read tool with an output schema, the description covers purpose, gating inputs, refinement inputs, return shape and alternatives. Minor gap: start_date/end_date participation-date semantics are left entirely to the schema, and no guidance on invalid combinations (e.g. start_date after end_date) is offered.

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 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema cannot express: city_id/category_id are the qualifying selectors ('at least one of'), while sort, price_min/price_max and page/per_page merely 'refine the same result set'. It also flags provenance of the id values (from klook_destinations / klook_attractions_categories).

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 ('Search') and a precisely bounded resource (the Klook attractions-ticket vertical, enumerated as theme parks, water parks, museums, observation decks), and describes the returned payload. It explicitly separates itself from klook_search (tours/experiences) and klook_search_filters (category ids/dates), so an agent can route 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 a concrete invocation precondition ('Provide at least one of city_id ... or category_id'), explains the fallback behavior when both are omitted is implied by the schema, and names two explicit alternatives with the condition that selects each. This is the strongest form of when-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.