Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

agoda_activities_search

Search Agoda activities by keyword, city, or city ID to retrieve tours, attractions, and experiences. When keyword is omitted, city name is used for general listings.

Instructions

Search Agoda activities. Returns Agoda activities (tours, attractions, experiences) matching a free-text keyword and/or a city. When keyword is omitted, the resolved city's name is used instead to return a general listing of activities in that city. Callers may supply a known Agoda city id or a free-text city name for the city filter; when both are supplied city_id takes precedence. Credential-free public data from Agoda's own destination search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoFree-text city name, used directly as the search text when keyword is omitted, and to resolve a city id filter.
city_idNoNumeric Agoda city id to filter results to. Optional if keyword is supplied; city_id takes precedence over city when both are supplied.
keywordNoFree-text activity search keyword. When omitted, the resolved city's name is used instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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. It discloses behavioral nuances: keyword fallback to resolved city name, city_id precedence, and credential-free public data sourcing. It stops short of describing pagination or result format, but for a search tool this is notably transparent.

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?

Four sentences, each packed with distinct information. Front-loaded verb and resource, no fluff, and the fallback/precedence rules are stated compactly without repetition.

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?

Given the tool's simplicity (3 optional params, no output schema), the description covers the main invocation patterns and parameter interactions. It could mention result structure or limits, but the core selection criteria are well addressed.

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 already covers all three parameters with descriptions, but the description adds meaningful behavioral semantics: how keyword omission triggers city-name search, and the city_id > city precedence rule. This goes beyond simple parameter mapping.

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: 'Search Agoda activities' and clarifies the result type as 'tours, attractions, experiences'. This clearly distinguishes the tool from the sibling agoda_activity_detail (which retrieves a single activity) and other Agoda search tools.

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?

Provides clear usage context: can search by keyword and/or city, fallback to city name when keyword is omitted, and city_id precedence over city. However, it does not explicitly name alternative tools or state when not to use this tool, so it misses the top tier for explicit exclusions.

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