Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

agoda_activities_search

Search Agoda tours, attractions, and experiences by keyword or city. Filter by Agoda city ID or city name; if no keyword is given, results list activities for that city.

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.

Input 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

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the result category and the keyword/city fallback and precedence rules, but omits pagination behavior, result limits, authentication requirements, rate limits, and what happens when no keyword or city is supplied.

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 sentences, front-loaded with the core action and result type. No filler, and the fallback/precedence logic is placed after the main purpose, making the definition easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has three optional parameters, no annotations, and no output schema. The description covers the broad result category and filter logic, but leaves the empty-input case, result shape, and pagination unspecified, which are relevant gaps when no output schema or annotations provide that context.

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 description coverage is 100%, so the schema already documents all three parameters. The description restates the city_id precedence and keyword fallback already present in the schema and adds no new syntax, format, or validation details.

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 ('Search Agoda activities') and enumerates the returned result types (tours, attractions, experiences), distinguishing it from Agoda hotels/homes/flights. It does not explicitly differentiate itself from sibling activities tools such as agoda_activity_detail or expedia_activities_search, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides conditional invocation logic: when keyword is omitted the city name is used, and city_id takes precedence over city when both are supplied. However, it does not state when to use this tool instead of agoda_activity_detail, expedia_activities_search, or other search siblings, nor whether a call with all parameters omitted is valid.

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