Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_orders

Fetch paginated Eventbrite orders for an event or organization, with filters for status, email, changed-since time, and refund request status.

Instructions

List orders for an event or organization.

ENDPOINT: GET /events/{event_id}/orders/ OR GET /organizations/{organization_id}/orders/

Returns paginated list of orders. Orders are private - only available to authorized users.

FILTERING OPTIONS:

  • status: Filter by order status

    • active: Attending orders

    • inactive: Not attending orders

    • both: All orders

    • all_not_deleted: Active and inactive, but not deleted

  • changed_since (datetime): Only orders changed on/after this time (ISO 8601)

  • last_item_seen (string): With changed_since, orders after this time with ID > last_item_seen

  • only_emails (array): Only include orders from these email addresses

  • exclude_emails (array): Exclude orders from these email addresses

  • refund_request_statuses (array, event only): Filter by refund status

    • completed, pending, outside_policy, disputed, denied

ORDER FIELDS RETURNED:

  • created, changed: Timestamps

  • name, first_name, last_name, email: Order owner info

  • costs: Complete breakdown (base_price, display_price, eventbrite_fee, payment_fee, tax, gross, discount_amount, discount_type)

  • event_id: Event ID

  • time_remaining: Seconds to complete

  • status: Order status

  • promo_code (optional): Discount code

RESPONSE:

  • orders (array): List of Order objects

  • pagination: Pagination information

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter: active, inactive, both, all_not_deleted
event_idNoEvent ID (use this OR organization_id)
only_emailsNoInclude these emails
changed_sinceNoISO 8601 datetime
exclude_emailsNoExclude these emails
last_item_seenNoFor pagination with changed_since
organization_idNoOrganization ID (use this OR event_id)
refund_request_statusesNoEvent only: completed, pending, outside_policy, disputed, denied

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.6/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 well: it discloses pagination, that orders are private and limited to authorized users, and the required Bearer token auth. It stops short of detailing rate limits, result caps, or error behavior.

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

Conciseness3/5

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

It is well-organized with labeled sections (FILTERING OPTIONS, RESPONSE, AUTHENTICATION), but it is quite long and spends a large block on ORDER FIELDS RETURNED, which overlaps with the RESPONSE/return-value territory. Some repetition of schema content reduces efficiency.

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 appropriately explains returned fields and the orders/pagination response shape, auth requirements, and filtering. It is fairly complete for an 8-parameter list tool, with only minor gaps such as pagination limits or default status behavior.

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%, so parameters are already documented. The description enumerates the filtering options and status enum values (active, inactive, both, all_not_deleted) and refund_request_statuses values, adding some enum clarity beyond the schema, but largely mirrors the schema fields. Baseline 3 is appropriate.

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?

States a specific verb (list) and resource (orders) with clear scoping to an event or organization. It does not differentiate from the sibling get_order (single order) beyond the plural resource name, so it falls short of the clearest sibling-aware framing.

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 event_id vs organization_id endpoints imply context, and status descriptions hint at use cases, but the description never explicitly says when to use this vs get_order or other listing tools. Usage is only implied.

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