create_share_listCreate a public shortlist URL of 1 to 20 experiences that expires after 30 days. Returns a private deletionToken; never show it publicly.
| Name | Required | Description | Default |
|---|---|---|---|
| currency | No | Display currency for prices. | EUR |
| experienceIds | Yes | 1 to 20 experience ids. |
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| url | Yes | ||
| expiresAt | Yes | ||
| deletionToken | Yes | Private. Needed to delete the list. Do not publish. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint=false annotation, the description discloses important behavioral facts: the URL is public, expires in 30 days, and returns a private deletionToken that must never be shown publicly. This materially informs safe usage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences deliver the core function, constraints, and a security warning. There is no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a create operation with a complete parameter schema and a documented return token, the description covers the key aspects: scope, expiry, and the sensitive deletionToken. Nothing needed to call the tool correctly seems missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with both parameters already documented (experienceIds and currency with enum). The description recaps the 1-20 count but adds no new semantic detail beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the action (create) and the resource (a public shortlist URL), and adds precise constraints: 1-20 experiences, 30-day expiry. It doesn't explicitly contrast with sibling tools like get_booking_link, but the unique function is apparent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives; the context in which a public shareable shortlist is desired is only implied by the verb 'create'. There is no mention of when not to use it or which sibling tools cover adjacent cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes: search, detail, reviews, compare, booking link, collections, and destinations each target a different operation. The only mild overlap is between get_booking_link and get_experience since get_experience already includes a booking URL, but the descriptions clarify the checkout-specific purpose.
Tool names overwhelmingly follow a clean snake_case verb_noun pattern: list_destinations, get_experience, search_experiences, create_share_list. The one deviation is nearest_destination, which uses an adjective_noun form instead of a verb, but it is still readable and predictable.
Eleven tools is well within the ideal range and each tool contributes to a coherent workflow: discovery, details, comparison, sharing, and booking links. No tool feels redundant or excessive, and the set is appropriately scoped for an experience-booking affiliate server.
The core lifecycle is well covered: find destinations, search experiences, inspect details, read reviews, compare options, generate booking links, and create shared shortlists. Minor gaps exist around shortlist management—there is no way to read or delete a created share list beyond its expiry—but agents can still complete the main user journey without dead ends.