Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

klook_interests

Retrieve Klook interest-topic landing pages with IDs, slugs, destination scopes, and URLs so you can choose interest tags for browsing search results.

Instructions

List Klook interest topics. Returns Klook's published interest-topic landing pages, read from its en-US interest sitemap. Each entry carries the interest id, the landing-page slug, the optional city id or country id the page is scoped to, and the absolute landing URL. The same interest id appears more than once: once unscoped, and again scoped to a country or a city, because each is a separately published landing page. Use an interest id as the interest_tag value with /klook/search (browse only, not with query); the context-scoped interest options for a specific destination are published by /klook/search/filters.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: names the upstream data source (en-US interest sitemap), and discloses the non-obvious duplicate-entry behavior (same interest id appears unscoped and again scoped to a country or city, each a separate landing page). It does not say whether results are cached, ordered, or stable over time, which is a minor remaining gap.

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, then return shape, then the duplicate-entry caveat, then the downstream tutorial — a sensible order with no filler sentences. The duplication explanation runs slightly long and restates 'separately published landing page' twice, which is the only trimming opportunity.

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?

No output schema exists, so the description must describe returns, and it does: it enumerates every field each entry carries and explains why ids repeat. Combined with the data source and the handoff to /klook/search and /klook/search/filters, an agent has everything needed to call it and interpret the result correctly.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The definition wisely spends its words on return-field semantics (interest id, slug, optional city/country id, absolute URL) instead of inventing parameter detail.

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?

Opens with a specific verb+resource: 'List Klook interest topics', then immediately narrows to 'published interest-topic landing pages, read from its en-US interest sitemap'. That distinguishes it cleanly from klook_search, klook_search_filters and klook_categories, which the agent would otherwise confuse with it.

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?

Explicitly routes downstream use: take an interest id as the interest_tag value for /klook/search with the constraint 'browse only, not with query', and states that context-scoped interest options for a destination come from /klook/search/filters instead. When-to-use-this vs use-another-tool is spelled out rather than implied.

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

Deploy Server