Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_event

Retrieve Eventbrite event details by ID, including dates, status, venue, organizer, and ticket availability, to display or manage a specific event.

Instructions

Retrieve an Event by Event ID.

ENDPOINT: GET /events/{event_id}/

NOTE: If the Event being retrieved was created using the new version of Create, then you may notice that the Event's description field is now being used to hold the event summary. To retrieve your event's fully-rendered HTML description, you will need to make an additional API call to retrieve the Event's full HTML description.

EVENT OBJECT - PUBLIC FIELDS:

  • name (multipart-text): Event name

  • summary (string, optional): Event summary. Short summary describing the event and its purpose

  • description (multipart-text, optional, DEPRECATED): Event description. Description can be lengthy and have significant formatting

  • url (string): URL of the Event's Listing page on eventbrite.com

  • start (datetime-tz): Event start date and time

  • end (datetime-tz): Event end date and time

  • created (datetime): Event creation date and time

  • changed (datetime): Date and time of most recent changes to the Event

  • published (datetime): Event publication date and time

  • status (string): Event status. Can be draft, live, started, ended, completed, canceled

  • currency (string): Event ISO 4217 currency code

  • online_event (boolean): true = Specifies that the Event is online only (i.e. the Event does not have a Venue)

  • hide_start_date (boolean): If true, the event's start date should never be displayed to attendees

  • hide_end_date (boolean): If true, the event's end date should never be displayed to attendees

EVENT OBJECT - PRIVATE FIELDS (only available to User):

  • listed (boolean): true = Allows the Event to be publicly searchable on the Eventbrite website

  • shareable (boolean): true = Event is shareable, by including social sharing buttons for the Event to Eventbrite applications

  • invite_only (boolean): true = Only invitees who have received an email inviting them to the Event are able to see Eventbrite applications

  • show_remaining (boolean): true = Provides, to Eventbrite applications, the total number of remaining tickets for the Event

  • password (string): Event password used by visitors to access the details of the Event

  • capacity (integer): Maximum number of tickets for the Event that can be sold to Attendees. The total capacity is calculated by the sum of the quantity_total of the Ticket Class

  • capacity_is_custom (boolean): true = Use custom capacity value to specify the maximum number of Attendees for the Event. False = Calculate the maximum number of Attendees for the Event from the total of all Ticket Class capacities

AVAILABLE EXPANSIONS: Use ?expand=expansion_name to include additional data:

  • logo: Event image logo

  • venue: Event Venue

  • organizer: Event Organizer

  • format: Event Format

  • category: Event Category

  • subcategory: Event Subcategory

  • bookmark_info: Indicates whether a user has saved the Event as a bookmark

  • refund_policy: Event Refund Policy

  • ticket_availability: Overview of availability of all Ticket Classes

  • external_ticketing: External ticketing data for the Event

  • music_properties: Event Music Properties

  • publish_settings: Event publish settings

  • basic_inventory_info: Indicates whether the event has Ticket Classes, Inventory Tiers, Donation Ticket Classes, Ticket Rules, Inventory Add-Ons, and/or Admission Inventory Tiers

  • event_sales_status: Event's sales status details

  • checkout_settings: Event checkout and payment settings

  • listing_properties: Display/listing details about the event

  • has_digital_content: Whether or not an event Has Digital Content

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the behavioral burden, and it does a lot: it documents the full field set, distinguishes public vs private fields (private only available to the authenticated user), and flags the deprecation/behavioral quirk where the summary occupies the description field. It also specifies the auth requirement. Missing rate limits and an explicit statement on pagination/error behavior keeps it from 5.

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

Conciseness2/5

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

The core operation is front-loaded in one good sentence, but the bulk of the description is a very long field dump and expansion list that dwarfs the actual guidance. For a single-parameter retrieval tool this is bloated and the important behavioral note is buried mid-document.

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?

There is no output schema, so the description must describe return values, and it enumerates the event object fields, marks public vs private, and lists all expansions with names and meanings. It also covers auth. It is essentially complete for calling the tool correctly, though the deprecation note could be clearer and error/rate behaviors are absent.

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 coverage is 100% for the single eventId parameter, so the baseline is 3. The description adds no parameter syntax or format detail beyond reiterating 'by Event ID', and the ?expand= list, while useful, is really a return-value modifier rather than a parameter explanation.

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: 'Retrieve an Event by Event ID.' The endpoint line GET /events/{event_id}/ pins down the exact operation, and the distinction from siblings such as get_event_description and list_events is implicit in the ID-based retrieval plus the note about fetching the full HTML description separately.

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

Usage Guidelines3/5

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

The description explains one important routing decision—that get_event returns the summary in the description field and a separate call is needed for the full HTML description (implying get_event_description). But it offers no guidance on when to use this versus get_event_series, get_organization, or list_events, and gives no conditions or exclusions.

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

Deploy Server

Other Tools