EcoAloha

Create share list

create_share_list

Create a public shortlist URL of 1 to 20 experiences that expires after 30 days. Returns a private deletionToken; never show it publicly. Offers are limited to reviewed physical tours and admissions. Editorial destinations do not guarantee app inventory. Digital-only and unreviewed products are unavailable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "experienceIds": "<experienceIds>"
    },
    "name": "create_share_list"
  }
}

Input Schema

Name	Required	Description	Default
`currency`	No	Display currency for prices.	EUR
`experienceIds`	Yes	1 to 20 experience ids.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 19, 2026

changedInput schema / properties / experienceIds / items / 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": {
+      "deletionToken": {
+        "description": "Private. Needed to delete the list. Do not publish.",
+        "type": "string"
+      },
+      "expiresAt": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "url",
+      "deletionToken",
+      "expiresAt"
+    ],
+    "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: -{
-  "deletionToken": {
-    "description": "Private. Needed to delete the list. Do not publish.",
-    "type": "string"
-  },
-  "expiresAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "id": {
-    "type": "string"
-  },
-  "url": {
-    "format": "uri",
-    "type": "string"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "id",
-  "url",
-  "deletionToken",
-  "expiresAt"
-]

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Consistent with annotations (readOnlyHint=false, destructiveHint=false), the description discloses key behavioral traits: the created URL expires after 30 days, the returned deletionToken is private and must not be shown publicly, and inventory availability is not guaranteed for editorial destinations. This adds meaningful context beyond the annotations regarding side effects and security handling.

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?

Three tight sentences: one for the core action and constraints, one for the critical token warning, and one for eligibility boundaries. There is no filler, and the most important information is front-loaded.

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 annotations provide the safety profile, the description covers all essential behavioral and eligibility information an agent needs to invoke the tool correctly: what it creates, expiration, token handling, and input restrictions. Nothing critical is missing.

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. The description adds value by explaining eligibility constraints on experienceIds (reviewed physical tours/admissions, unavailable digital-only and unreviewed products), which goes beyond the schema's simple pattern and item descriptions. This contextualizes both parameters without adding redundant detail.

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 and resource: 'Create a public shortlist URL of 1 to 20 experiences.' It immediately distinguishes itself from sibling tools by describing a unique creation action with concrete constraints (expires after 30 days, returns a deletionToken). No ambiguity remains about what is being produced.

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?

Provides clear eligibility context: offers are limited to reviewed physical tours and admissions, and digital-only/unreviewed products are unavailable. This tells the agent when this tool applies and what inputs it will accept, though it does not explicitly name alternative tools for ineligible cases.

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.