Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_order

Retrieve an Eventbrite order by Order ID to check its status, cost breakdown, and transaction details.

Instructions

Retrieve an Order by Order ID.

ENDPOINT: GET /orders/{order_id}/

The Order object represents an order made against Eventbrite for one or more Ticket Classes. A single Order can be made up of multiple tickets. Contains Order's financial and transactional information. Use Attendee object for attendee information.

Order objects are private - only available to User and Order owner.

ORDER FIELDS:

  • created (datetime): When Order was placed and Attendee created

  • changed (datetime): Last change to Attendee

  • name (string): Order owner name (use instead of first_name/last_name)

  • first_name (string): Order owner first name (deprecated, use name)

  • last_name (string): Order owner last name (deprecated, use name)

  • email (string): Order owner email

  • costs (object): Cost breakdown

  • event_id (string): Order's Event ID

  • time_remaining (number): Time to complete Order (seconds)

  • questions (array, optional): Custom questions for Order owner

  • answers (array, optional): Answers to custom questions

  • promo_code (string, optional): Discount code applied

  • status (string): Order status

ORDER COSTS BREAKDOWN:

  • base_price (currency): Amount without fees/tax (use display_price if include_fee used)

  • display_price (currency): Correct amount when include_fee used

  • display_fee (currency): Fees/tax included (absorbed) in displayed price

  • gross (currency): Total Order amount

  • eventbrite_fee (currency): Eventbrite fee (don't expose to Order owner)

  • payment_fee (currency): Payment processor fee

  • tax (currency): Tax amount

  • display_tax (object): Tax with name

  • price_before_discount (currency): Price before discount applied

  • discount_amount (currency): Total discount (if applied)

  • discount_type (string): coded, access, public, hold, or null

  • fee_components (list): Fee cost components

  • tax_components (list): Tax cost components

  • shipping_components (list): Shipping cost components

  • has_gts_tax (boolean): Has GTS tax

  • tax_name (string): Tax name if applicable

AVAILABLE EXPANSIONS:

  • event: Order's Event

  • attendees: Order's Attendees

  • merchandise: Merchandise in Order

  • concierge: Order's concierge

  • refund_requests: Order's refund request

  • survey: Order's custom questions

  • survey_responses: Responses to survey questions

  • answers: Answers to custom questions

  • ticket_buyer_settings: Purchaser information including confirmation messages

  • contact_list_preferences: Email opt-in preferences

POSSIBLE ERRORS (400):

  • ORDER_EXPIRED: The order is expired

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the access-control constraint ('private - only available to User and Order owner'), the required Bearer authentication, and a concrete error behavior (ORDER_EXPIRED at 400). It omits rate limits and pagination behavior, but the behavioral coverage is notably richer than a bare read tool.

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

Conciseness4/5

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

Purpose and endpoint are front-loaded, then well-delimited sections follow. The lengthy field and expansion documentation is heavy but earns its place because there is no output schema to convey return shape; still, the volume is higher than strictly needed.

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?

With no output schema, the description compensates by enumerating return fields, cost breakdown, and available expansions, plus auth and error conditions. An agent has everything needed to call and interpret this endpoint correctly.

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% for the single order_id parameter, so the schema already documents it fully. The description adds no format or syntax detail beyond 'by Order ID', so baseline 3 applies.

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 opening line states a specific verb and resource scoped by identifier ('Retrieve an Order by Order ID'), which an agent can immediately distinguish from the list_orders sibling. The scope constraint is front-loaded and unambiguous.

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?

It implicitly tells the agent this is the single-order-by-ID path and adds a routing hint ('Use Attendee object for attendee information'), but never explicitly contrasts itself with list_orders or state when-not to use it. Usage is inferable but not spelled out.

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