Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

booking_attractions_search

Search Booking.com attractions for a destination and date range, with optional category or subcategory filters to narrow things to do.

Instructions

Search Booking.com attractions. Returns Booking.com attractions/things-to-do search results for a destination and date range, with an optional category/subcategory filter and a discoverable category taxonomy.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based result page, default 1
limitNoResults per page, 1-30, default 15
queryYesDestination name or city
categoryNoOptional top-level category tagname filter, from a prior response's categories
end_dateNoAvailability end date, YYYY-MM-DD, defaults to start_date
start_dateYesAvailability start date, YYYY-MM-DD
subcategoryNoOptional subcategory tagname filter, from a prior response's categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that results are availability-scoped to a date range and that the category taxonomy is discoverable from responses, which is useful, but says nothing about read-only safety, permissions, pagination, or result contents.

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?

Two compact sentences, front-loaded with the purpose, with no redundant restatement. Efficient though the second sentence slightly over-describes the taxonomy feature.

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?

Reasonable for a 7-param search with no annotations and no output schema, but the return shape is only gestured at ('search results') and pagination behavior is left entirely to the schema, so there is room to do more.

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 meaning by framing start/end dates as an availability window and by explaining that category and subcategory are discoverable tagnames sourced from prior responses, which the schema alone only hints at.

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 (Search) and resource (Booking.com attractions) and clarifies output is attractions/things-to-do results. It does not explicitly differentiate from close siblings like booking_attractions_detail or booking_attractions_reviews, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Provides no when-to-use guidance or alternatives. The mention that category/subcategory come 'from a prior response's categories' is a mild hint at a discovery flow, but nothing tells the agent when to prefer this over the detail/reviews siblings.

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