Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

booking_attractions_detail

Fetch full details for a Booking.com attraction by slug, including name, price, duration, reviews, and city. Use the returned id to get attraction reviews.

Instructions

Booking.com attraction detail. Returns the details of one Booking.com attraction by slug, taken from products[].slug in a booking-attractions-search result: name, short_description, description, duration, price with currency, review_score, review_count and city. The returned id is the product_id for booking-attractions-reviews.

Input Schema

NameRequiredDescriptionDefault
slugYesAttraction slug, from a prior attraction search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 full burden. It usefully enumerates the returned fields (name, description, duration, price/currency, review_score, review_count, city) and the chaining id, but says nothing about error handling, missing-slug behavior, or any access constraints.

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?

Two dense, front-loaded sentences. The purpose leads, the field enumeration earns its place given there is no output schema, and nothing is redundant.

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?

With no output schema, the description correctly compensates by listing return fields and the id's downstream use, and it documents the only parameter's origin. It is nearly complete for a single-item detail endpoint, with only operational behaviors left unaddressed.

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 already 100% for the single slug param, but the description adds real value beyond the schema by naming the exact source path (products[].slug) and the sibling tool that produces it, which the schema's generic 'from a prior attraction search result' does not pin down.

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?

States a specific verb+resource ('Returns the details of one Booking.com attraction by slug') and scopes it to a single entity, distinguishing it cleanly from the booking-attractions-search and booking-attractions-reviews siblings.

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?

Tells the agent exactly where the required slug comes from ('products[].slug in a booking-attractions-search result') and how the result chains into booking-attractions-reviews, which is strong contextual routing. It does not explicitly state when not to use this tool, but the sequencing guidance is clear.

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