EcoAloha

Get booking link

get_booking_link

Get the Viator booking page URL for one experience. This is an affiliate link; it does not book or charge. Present the disclosure to the user. Offers are limited to reviewed physical tours and admissions. Editorial destinations do not guarantee app inventory. Digital-only and unreviewed products are unavailable.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`currency`	No	Display currency for prices.	EUR
`experienceId`	Yes	Reviewed physical-experience id from search_experiences. Unreviewed ids are rejected.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 19, 2026

changedInput schema / properties / experienceId / description

Previous value: -"Experience id (Viator product code) from search_experiences."New value: +"Reviewed physical-experience id from search_experiences. Unreviewed ids are rejected."

Changed3 schema fields changedSep 19, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "affiliate": {
+        "const": true,
+        "type": "boolean"
+      },
+      "disclosure": {
+        "type": "string"
+      },
+      "experienceId": {
+        "description": "Viator product code, for example 5010SYDNEY.",
+        "examples": [
+          "5010SYDNEY"
+        ],
+        "pattern": "^[A-Za-z0-9_-]{1,80}$",
+        "type": "string"
+      },
+      "url": {
+        "description": "Viator affiliate product page. Booking and payment happen on Viator.",
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "url",
+      "experienceId",
+      "affiliate",
+      "disclosure"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "availableTools": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "code": {
+        "type": "string"
+      },
+      "docs": {
+        "format": "uri",
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "retryAfterSeconds": {
+        "type": "integer"
+      },
+      "status": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "code",
+      "message",
+      "status"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "affiliate": {
-    "const": true,
-    "type": "boolean"
-  },
-  "disclosure": {
-    "type": "string"
-  },
-  "experienceId": {
-    "description": "Viator product code, for example 5010SYDNEY.",
-    "examples": [
-      "5010SYDNEY"
-    ],
-    "pattern": "^[A-Za-z0-9_-]{1,80}$",
-    "type": "string"
-  },
-  "url": {
-    "description": "Viator checkout page.",
-    "format": "uri",
-    "type": "string"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "url",
-  "experienceId",
-  "affiliate",
-  "disclosure"
-]

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: the URL is an affiliate link, it does not book or charge, the disclosure must be presented to the user, and product eligibility is limited. This meaningfully clarifies side-effect and safety expectations. No contradiction with annotations 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 front-loaded with the core function and each subsequent sentence adds necessary information: affiliate behavior, disclosure requirement, and eligibility constraints. There is no filler or repetition.

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

Completeness5/5

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

Given the output schema exists and the parameter schema is complete, the description covers the remaining operational context: what the link does, what it does not do, and which products are eligible. An agent has enough to invoke the tool correctly.

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 experienceId and currency well. The description does not add parameter-level detail beyond what the schema provides, which matches the baseline of 3.

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?

The description states a specific verb and resource: 'Get the Viator booking page URL for one experience.' It is clearly distinct from siblings like compare_experiences or search_experiences by focusing on the booking page URL, though it never names an alternative explicitly.

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?

The description gives clear context for when the tool is appropriate: generating an affiliate booking link that does not book or charge, and only for reviewed physical tours and admissions. It does not explicitly contrast this tool with a sibling alternative, but the eligibility constraints effectively bound usage.

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

All EcoAloha tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.