Skip to main content
Glama

search_attractions

Search real-time attractions, tours, and activities on booking.com. Returns activity name, price, description, rating, duration, and booking links.

Instructions

Search real-time attractions, tours, and activities on booking.com via AgentWeb. Returns activity name, price, description, rating, duration, free cancellation status, discounts, and booking links. Results in ~2 seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destinationYesCity name (e.g. 'Rome', 'Tokyo', 'Barcelona')
dateYesDate in YYYY-MM-DD format
end_dateNoEnd date in YYYY-MM-DD format (defaults to same as date)
sortNoSort results (default: popular)popular
limitNoMaximum results to return (default: 15)
Behavior3/5

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

No annotations are present, so the description alone must convey behavioral traits. It mentions 'real-time' and '~2 seconds' but lacks details on authentication, rate limits, or behavior when no results are found.

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?

The description is two sentences that efficiently state purpose, return data, and performance. No filler, structured with front-loaded key information.

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?

The description covers purpose, return fields, and performance, which is adequate for a search tool. However, missing details on output structure (e.g., object shape) and error handling reduce completeness slightly.

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 baseline is 3. The description adds a list of return fields but does not enhance parameter meaning beyond what the schema already provides.

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 clearly states the verb 'Search' and resource 'attractions, tours, and activities' on booking.com via AgentWeb. It distinguishes from sibling tools like search_flights and search_hotels by specifying activity type.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The name and sibling context imply it's for activities, but the description does not directly instruct when to choose this over alternatives like search_hotels.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zerabic/agentweb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server