tickadoo Experiences and Events

render_experience_cards

Read-onlyIdempotent

Use when visual cards would help present a discovery result from a supported search tool. Pass the product_id values from that result as experience_ids, never full product rows, and choose a render_type. Optionally pass render_context.intent_summary (a short phrase describing what the user asked for, such as city, date, or audience) to set the heading. Keep each result set to one card view to avoid duplicate cards; concise text context may accompany it.

Input Schema

Name	Required	Description
`render_type`	Yes	Visual layout requested for the widget.
`experience_ids`	Yes	The stable product_id values from search_experiences results (the product_id field of each returned row). Pass IDs only, never full product rows.
`render_context`	No	Optional rendering hints that shape the card heading and sort explanation: intent_summary, date_hint, audience_hint, sort_basis.
`idempotency_key`	No	Optional UUID. Reuse for identical card render responses within five minutes.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

addedInput schema / properties / render_context / description

Added value: +"Optional rendering hints that shape the card heading and sort explanation: intent_summary, date_hint, audience_hint, sort_basis."

Changed4 schema fields changedSep 3, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / oneOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "experience_ids": {
+        "description": "The stable product ids rendered as cards.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "experience_ids"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "detail": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "error_type": {
+        "enum": [
+          "ambiguous_input",
+          "invalid_input",
+          "rate_limited",
+          "supplier_unavailable",
+          "circuit_breaker_open",
+          "partial_result",
+          "unauthorized",
+          "forbidden",
+          "internal_error",
+          "not_found"
+        ],
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "retry_after": {
+        "type": "string"
+      },
+      "retry_after_seconds": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "schema_version": {
+        "const": "https://mcp.tickadoo.com/schemas/tool_error/1.0"
+      }
+    },
+    "required": [
+      "schema_version",
+      "error_type",
+      "message",
+      "detail"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "experience_ids": {
-    "description": "The stable product ids rendered as cards.",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "experience_ids"
-]

Changed1 schema field changedJul 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "experience_ids": {
+      "description": "The stable product ids rendered as cards.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "experience_ids"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 31, 2026

changedInput schema / required

Previous value: -[
-  "experience_ids",
-  "render_type",
-  "render_context"
-]New value: +[
+  "experience_ids",
+  "render_type"
+]

Changed1 schema field changedMay 27, 2026

changedInput schema / properties / experience_ids / description

Previous value: -"Stable product IDs from search_experiences. Pass IDs only, never full product rows."New value: +"The stable product_id values from search_experiences results (the product_id field of each returned row). Pass IDs only, never full product rows."

AddedApr 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, idempotentHint, openWorldHint=false), and the description adds real behavioral constraints beyond them: pass only product_id values and never full product rows, and render a single card view per result set to avoid duplicate cards. It omits any mention of the idempotency_key reuse window, which is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use condition, then parameter guidance, then the duplicate-avoidance constraint; every sentence carries an instruction. It is slightly dense and could be tightened, but there is no filler.

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?

An output schema exists so return values need no explanation, and the description covers trigger, ID-sourcing, render_type selection, optional context, and duplicate avoidance for a 4-parameter nested-schema tool. Only the idempotency_key behavior is left entirely to the schema.

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, but the description adds meaningful semantics: it maps experience_ids to 'the product_id values from that result' and clarifies that render_context (whose inner intent_summary is required by the schema) is itself optional and used to set the heading. The 'never full product rows' warning guards a real misuse mode not stated in the schema.

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 frames the tool as a rendering/presentation step for a 'discovery result from a supported search tool', which distinguishes it from the many search_*/get_* siblings that produce results rather than display them. The action verb is implicit ('cards would help present') rather than stated as 'renders cards', so it is clear but slightly trigger-phrased rather than action-phrased.

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?

Gives a clear when-to-use condition ('when visual cards would help present a discovery result') plus an operating constraint ('keep each result set to one card view to avoid duplicate cards'). It does not name a specific alternative or state when-not to render, so it falls short of explicit routing guidance.

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

All tickadoo Experiences and Events 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.