Skip to main content
Glama

search_events

Read-onlyIdempotent

Find live events in any city, including concerts, sports, theater, and comedy. Filter by date, category, and keyword to discover shows or games during your trip.

Instructions

Search live events, concerts, sports games, theater, comedy, and shows in a city (Ticketmaster + SeatGeek catalog). Filter by city, date range, category (music / sports / arts / theater / family / comedy), and keyword (artist name, team name, show title). Use this when the user wants tickets to a concert, a sports game, a Broadway show, or any live event during their trip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesCity name (e.g., 'New York', 'Las Vegas', 'London')
date_fromYesStart date (YYYY-MM-DD)
date_toNoOptional end date (YYYY-MM-DD)
categoryNoOptional category filter — comma-separated list. Values: 'music', 'sports', 'arts', 'theater', 'family', 'comedy'
keywordNoOptional keyword search (artist name, team, show title)

Implementation Reference

  • Input schema definition for the 'search_events' tool. Defines required (city, date_from) and optional (date_to, category, keyword) parameters for searching live events via Ticketmaster + SeatGeek.
      name: "search_events",
      description:
        "Search live events, concerts, sports games, theater, comedy, and shows in a city (Ticketmaster + SeatGeek catalog). Filter by city, date range, category (music / sports / arts / theater / family / comedy), and keyword (artist name, team name, show title). Use this when the user wants tickets to a concert, a sports game, a Broadway show, or any live event during their trip.",
      inputSchema: {
        type: "object" as const,
        properties: {
          city: { type: "string", description: "City name (e.g., 'New York', 'Las Vegas', 'London')" },
          date_from: { type: "string", description: "Start date (YYYY-MM-DD)" },
          date_to: { type: "string", description: "Optional end date (YYYY-MM-DD)" },
          category: { type: "string", description: "Optional category filter — comma-separated list. Values: 'music', 'sports', 'arts', 'theater', 'family', 'comedy'" },
          keyword: { type: "string", description: "Optional keyword search (artist name, team, show title)" },
        },
        required: ["city", "date_from"],
      },
    },
  • src/server.ts:510-510 (registration)
    Tool annotation registration for 'search_events' in the TOOL_ANNOTATIONS record, providing metadata (title, readOnlyHint, etc.) required by the Anthropic Connector Directory.
    search_events: { title: "Search Live Events & Tickets", readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
  • Handler implementation for 'search_events'. Calls POST /v1/events/search via the apiCall helper, then trims the response using trimEventResponse and returns the result as text content.
    case "search_events": {
      const result = await apiCall("POST", "/v1/events/search", args);
      const trimmed = trimEventResponse(result);
      return { content: [{ type: "text", text: JSON.stringify(trimmed, null, 2) }] };
    }
  • The trimEventResponse helper function that reduces raw event API responses down to key fields (event_id, name, category, venue, city, date, time, price_min_usd, price_max_usd, url, thumbnail) with a limit of 25 items.
    function trimEventResponse(raw: any, limit = 25): any {
      const data = Array.isArray(raw?.data) ? raw.data : [];
      const trimmed = data.slice(0, limit).map((e: any) => ({
        event_id: e.event_id || e.id,
        name: e.name || e.title,
        category: e.category || e.type,
        venue: e.venue || e.venue_name,
        city: e.city,
        date: e.date || e.start_date || e.local_date,
        time: e.time || e.local_time,
        price_min_usd: e.price_min_usd || e.price?.min,
        price_max_usd: e.price_max_usd || e.price?.max,
        url: e.url || e.purchase_url,
        thumbnail: e.thumbnail || (typeof e.images?.[0] === "string" ? e.images[0] : e.images?.[0]?.url),
      }));
      return {
        data: trimmed,
        meta: { count: trimmed.length, total_returned: data.length, trimmed_for_llm: data.length > limit },
      };
    }
Behavior4/5

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering safety and idempotency. The description adds that it searches a combined catalog from Ticketmaster and SeatGeek and supports filtering, which supplements annotations without contradicting them.

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 two sentences: first defines scope and source, second gives usage guidance. Every sentence adds value, no redundancy or fluff.

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 tool's 5 parameters (2 required), no output schema, and sibling tools covering other travel needs, the description fully equips an agent to understand purpose, parameters, and when to invoke it.

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%, and the description essentially re-lists parameters (city, date range, category, keyword) with examples. It adds marginal value by providing example values for category and keyword, but does not significantly enhance what the schema already provides.

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 it searches live events (concerts, sports, theater, etc.) in a city, explicitly listing event types and data sources (Ticketmaster + SeatGeek). This distinguishes it from sibling tools like search_activities or search_dining.

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 second sentence explicitly advises using this tool 'when the user wants tickets to a concert, a sports game, a Broadway show, or any live event during their trip.' It provides clear context for use but does not explicitly mention when not to use it or name alternatives.

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/Autonomad1/autonomad-travel'

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