Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

klook_activity

Fetch the public Klook card record for one activity by activity_id from /klook/search, returning title, destination, price, rating, reviews, image, coordinates and tags.

Instructions

Get a Klook activity card. Returns the public card-level record for one Klook activity: title, destination, price, rating, review count, image, coordinates and tags. Use an activity_id from /klook/search. This is Klook's card surface; the full detail page payload is behind Klook's bot defense and is not served.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "klook_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYesKlook activity id from /klook/search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/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 does disclose a real behavioral limit: only the public card-level record is served and the full detail payload is blocked. It implies a safe read ('public card-level record') but does not state auth requirements, rate limits, or what happens with an invalid activity_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose, then the return contents, then the id source and the known limitation. Every sentence adds information an agent needs; nothing is padding.

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 one-parameter read tool with no output schema, the description covers purpose, the source of the id, the returned field list, and the key caveat that richer data is not available. An agent has everything needed to call it correctly and interpret the result.

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 there is a single required parameter already documented in the schema. The description only repeats the schema's provenance note ('Use an activity_id from /klook/search') and adds no format, range, or validity details beyond it.

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?

States a specific verb and resource ('Get a Klook activity card') and enumerates the returned fields, so an agent knows exactly what comes back. It does not explicitly differentiate itself from siblings such as klook_reviews or klook_search_unified, so it stops short of 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?

Gives clear context: the id must come from /klook/search, and the full detail-page payload is explicitly unavailable due to bot defense, which prevents an agent from hunting for a richer endpoint. No explicit exclusion of named sibling tools, 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