Skip to main content
Glama

list_events

Retrieve a paginated list of events for a specific organization, with optional filters for status, sorting, and page size. Use it to browse or manage an organization's Eventbrite events.

Instructions

List Events by Organization ID. Returns a paginated response.

ENDPOINT: GET /organizations/{organization_id}/events/

PARAMETERS:

  • organization_id (string, required): Organization ID

  • name_filter (string, optional): Filter Organization's Events by specified name

  • currency_filter (string, optional): Filter Organization's Events by specified currency (e.g., USD)

  • order_by (enum, optional): Sort order for the list of Events • start_asc, start_desc, created_asc, created_desc, name_asc, name_desc

  • series_filter (array[enum], optional): Filter based on whether an event is not a series, a series, child series or parent series. This filter has higher precedence than show_series_parent filter. Default will use show_series_parent filter behavior. • allevents: non-series & child series & parent series. Equivalent to [children,parents,nonseries] or [allevents,nonseries] • children: only child series • parents: only parent series • nonseries: non-series events • allseries: only series events. Equivalent to [children,parents]

  • show_series_parent (boolean, optional): false (Default) = In the list, show the series children and not series parent. true = In the list, show the series parent instead of series children.

  • status (enum, optional): Filter Organization's Events by status. Specify multiple status values as a comma delimited string. • draft: A preliminary form of a possible future Event • live: The Event can accept registrations or purchases if ticket classes are available • started: The Event start date has passed • ended: The Event end date has passed • completed: The funds for your Event have been paid out • canceled: The Event has been canceled • all: List Events with any status

  • event_group_id (string, optional): Filter Organization's Events by event_group_id

  • collection_id (string, optional): Filter Organization's Events by collection_id

  • page_size (number, optional): Number of records to display on each page of the list (default: 50)

  • time_filter (string, optional): Limits the list results to either past or current and future Events • all, past, current_future

  • venue_filter (array, optional): Filter Organization's Events by Venue ID

  • organizer_filter (array, optional): Filter Organization's Events by Organizer ID

  • inventory_type_filter (array[enum], optional): Filter Organization's Events by Inventory Type • limited: limited quantity inventory/GA • reserved: Reserved inventory • externally_ticketed: Externally ticketed event (no inventory)

  • event_ids_to_exclude (array[string], optional): IDs of events to exclude from the Organization's Events list

  • event_ids (array[string], optional): IDs of events to include from the Organization's Events list

  • collection_ids_to_exclude (array[string], optional): IDs of collections to exclude from the Organization's Events list. This will have precedence over event_group_id filter and collection_id filter.

ERROR RESPONSES:

  • 400 ARGUMENTS_ERROR: There are errors with your arguments

  • 404 NOT_FOUND: The organization_id you requested does not exist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter events by status
orderByNoSort order for the list of Events
pageSizeNoNumber of records to display on each page (default: 50)
continuationNoContinuation token for pagination
organizationIdNoOrganization ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the GET endpoint, pagination, default series behavior, and 400/404 error responses, but it omits authentication requirements, rate limits, and other operational constraints.

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 first sentence is clear and front-loaded, but the bulk of the description is a long parameter section that largely duplicates the schema and includes many parameters that do not exist in the tool's actual input schema. This makes it overly verbose for an MCP definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides rich API-style context, but it is not aligned with the actual input schema: it omits the continuation token and documents many non-schema filters. For a tool with no annotations and no output schema, this mismatch leaves the definition unreliable for accurate invocation.

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%, so the baseline is 3. The description adds enum meanings for status and order values, but its parameter list names many parameters not present in the actual input schema and uses mismatched names such as organization_id versus organizationId.

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 states a specific verb (List), resource (Events), and scope (by Organization ID), which separates it from siblings like get_event and list_events_by_series. An agent can identify the core operation without opening the schema.

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

Usage Guidelines2/5

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

The description explains filters and precedence but never states when to use list_events versus alternatives such as list_events_by_series or get_event. It provides parameter behavior rather than usage routing.

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