Skip to main content
Glama

get_experience_details

Read-only

Retrieve availability, venue information, and images for specific experiences on tickadoo® to support booking decisions.

Instructions

Get detailed availability, venue details, and images for a specific tickadoo® experience. Prefer passing the tickadoo slug or booking URL path; provider and provider_id are legacy fallback inputs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoPreferred: tickadoo slug or path, e.g. 'london-dungeon-tickets' or '/london/london-dungeon-tickets'
providerNoLegacy fallback only: hidden provider name used internally
provider_idNoLegacy fallback only: hidden provider-specific product ID
daysNoNumber of days of availability to fetch (default 30, max 180)
languageNoReserved for future language-aware API supporten

Implementation Reference

  • The implementation of the `get_experience_details` MCP tool, which resolves an experience from a slug or ID and fetches its detailed data.
    server.tool(
      "get_experience_details",
      "Get detailed availability, venue details, and images for a specific tickadoo® experience. Prefer passing the tickadoo slug or booking URL path; provider and provider_id are legacy fallback inputs.",
      {
        slug: z.string().optional().describe("Preferred: tickadoo slug or path, e.g. 'london-dungeon-tickets' or '/london/london-dungeon-tickets'"),
        provider: z.string().optional().describe("Legacy fallback only: hidden provider name used internally"),
        provider_id: z.string().optional().describe("Legacy fallback only: hidden provider-specific product ID"),
        days: z.number().int().min(1).max(180).optional().default(30).describe("Number of days of availability to fetch (default 30, max 180)"),
        language: z.string().optional().default("en").describe("Reserved for future language-aware API support"),
      },
      READ_ONLY_TOOL_ANNOTATIONS,
      async ({ slug, provider, provider_id, days, language }) => {
        try {
          let resolved: ResolvedProduct | undefined;
          let providerName = provider;
          let providerId = provider_id;
    
          if (slug?.trim()) {
            resolved = await resolveProductBySlug(slug, language);
            providerName = resolved.product.provider;
            providerId = resolved.product.providerId;
          } else if (!providerName || !providerId) {
            return createTextResponse("Error: Provide a tickadoo slug (preferred) or both provider and provider_id.", { isError: true });
          }
    
          const details = await getExperienceDetails(providerName, providerId, days);
          return createTextResponse(
            [
              resolved ? `🎭 ${resolved.product.title}` : "",
              formatExperienceDetails(days, details),
              resolved ? `   🔗 ${buildBookingUrl(resolved.bookingPath)}` : "",
            ].filter(Boolean).join("\n"),
            {
              structuredContent: {
                source: "tickadoo",
                slug: resolved?.product.slug,
                tickadooProductId: resolved?.product.id,
                bookingUrl: resolved ? buildBookingUrl(resolved.bookingPath) : undefined,
                days,
                details,
              },
            },
          );
        } catch (error) {
          return createTextResponse(`Error: ${getErrorMessage(error)}`, { isError: true });
        }
      },
    );
  • The underlying API function that fetches the structured experience data from the backend.
    export async function getExperienceDetails(
      provider: string,
      providerId: string,
      days: number,
    ): Promise<StructuredDataResponse> {
      return fetchJson<StructuredDataResponse>("/api/products/structured-data", {
        Provider: normalizeProviderName(provider),
        Id: providerId,
        Days: days.toString(),
      });
    }
Behavior4/5

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

Annotations indicate read-only, non-destructive, and open-world behavior, which the description does not contradict. It adds context by specifying input preferences and the scope of data fetched (availability, venue details, images), enhancing understanding beyond the annotations.

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 purpose and usage guidelines in two concise sentences, with no wasted words. Every sentence contributes directly to tool understanding and selection.

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?

Given the tool's complexity (5 parameters, no output schema) and rich annotations, the description is mostly complete. It covers purpose, usage, and input semantics well, but could benefit from mentioning potential outputs or limitations, though annotations help mitigate this gap.

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?

With 100% schema description coverage, the schema fully documents all parameters. The description adds value by clarifying input preferences (slug as preferred, provider/provider_id as legacy fallbacks) but does not provide additional semantic details beyond what the schema already covers.

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 specific action ('Get detailed availability, venue details, and images') and the resource ('a specific tickadoo® experience'), distinguishing it from sibling tools like find_nearby_experiences, list_cities, and search_experiences by focusing on details for a single experience rather than searching or listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance on when to use this tool by specifying preferred inputs ('tickadoo slug or booking URL path') and fallback options ('provider and provider_id are legacy fallback inputs'), helping the agent choose this over alternatives for retrieving detailed information on a known experience.

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/tickadoo/tickadoo-mcp'

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