Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

klook_reviews

List recent Klook reviews for a city and choose the experiences or attractions feed to retrieve reviewed activity titles, URLs, scores, review text, and timestamps.

Instructions

List recent Klook reviews for a city. Returns recent review cards from Klook's city-level review feed for one product vertical: the reviewed activity title and URL, the review score, the review text and its timestamp. Reviewer display names are deliberately not returned because they are personal data, even when Klook masks them. Vertical experiences (the default) reads Klook's experiences review feed and attractions reads its attractions review feed; the two feeds are separate inventories. Use a city_id from /klook/destinations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city_id": "<city_id>"
    },
    "name": "klook_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
city_idYesKlook city id from /klook/destinations
verticalNoReview feed to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description takes on the full disclosure burden and does most of it: it states this is a feed read, enumerates return fields, and explicitly explains that reviewer display names are deliberately omitted for privacy — a behavior an agent could not infer from schema alone. Gaps remain around recency window ("recent" is undefined), result count, and pagination, which keeps it at 4.

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 definition is front-loaded with purpose and return contents, then the vertical-mode explanation, then the city_id prerequisite — a sensible order with no filler sentences. It is slightly longer than needed; the closing "Use a city_id from /klook/destinations" restates the schema's own parameter description.

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?

There is no output schema, and the description compensates by listing the returned fields, plus the privacy exclusion and feed-selection semantics. It is complete enough to call correctly, but leaves volume and pagination behavior unspecified, which matters for a "list recent" feed.

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 real meaning beyond the schema: it states that experiences is the default vertical, that the two verticals are independent inventories rather than filters over one dataset, and that city_id must come from /klook/destinations. That default-value and dataset-separation context is not present in the schema's terse "Review feed to read".

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 opens with a specific verb and resource ("List recent Klook reviews for a city") and immediately scopes it to a city-level feed for one product vertical. It enumerates the returned fields (activity title/URL, score, text, timestamp), so an agent knows exactly what this tool yields versus general search or activity-detail 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 gives clear preconditions ("Use a city_id from /klook/destinations") and explains how to choose between the two feed modes, including which is the default and that the feeds are separate inventories. It stops short of naming any alternative tool or an explicit when-not condition, so 4 rather than 5.

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