Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_ticket_class

Modify an existing Eventbrite ticket class by updating fields such as name, cost, quantity, sales dates, or visibility for an event.

Instructions

Update an existing Ticket Class for an event.

ENDPOINT: POST /events/{event_id}/ticket_classes/{ticket_class_id}/

Supports partial updates. After May 7, 2020, inventory_tier_id is required for tiered events.

TICKET CLASS OBJECT - PUBLIC FIELDS (can be updated):

  • name (string): Ticket Class name

  • description (string): Ticket Class description

  • sorting (integer): Order in purchase flow

  • cost (currency): Display cost (format: "CURRENCY,amount_in_cents" e.g., "USD,1000" for $10.00)

  • donation (boolean): Is donation ticket

  • free (boolean): Is free ticket

  • minimum_quantity (integer): Minimum tickets per Order

  • maximum_quantity (integer): Maximum tickets per Order

  • delivery_methods (array): electronic, will_call, standard_shipping, third_party_shipping

  • image_id (string): Image ID for ticket class

TICKET CLASS OBJECT - PRIVATE FIELDS (can be updated):

  • quantity_total (integer): Total number available

  • capacity (integer): Number available for sale

  • hidden (boolean): Hidden from public

  • sales_start (string): When sales begin (ISO 8601 datetime)

  • sales_end (string): When sales end (ISO 8601 datetime)

  • sales_start_after (string): Ticket Class ID that triggers sales start

  • include_fee (boolean): Fee included in price (cannot use with split_fee)

  • split_fee (boolean): Fee shown separately

  • hide_description (boolean): Hide description on listing page

  • hide_sale_dates (boolean): Hide sale dates on event page

  • auto_hide (boolean): Hide when not for sale

  • auto_hide_before (datetime): Override auto-hide disable time

  • auto_hide_after (datetime): Override auto-hide enable time

  • inventory_tier_id (string): Inventory tier ID (required for tiered events)

  • order_confirmation_message (string): Message when Order completed

  • secondary_assignment_enabled (boolean): Secondary barcode assignment (RFID)

POSSIBLE ERRORS (400):

  • AUTO_HIDE_NOT_SET: Must select auto hide setting

  • BAD_QUANTITIES: Sum of tickets doesn't equal total available

  • COST_GREATER_THAN_FEE: Cost must be greater than fee

  • CURRENCY_MISMATCH: Event and ticket currency must match

  • DONATION_AND_COST: Cannot be both donation and charged ticket

  • DONATION_AND_FREE: Cannot be both donation and free ticket

  • DONATION_AND_MIN_QUANTITY: Set minimum quantity for donation ticket

  • FREE_AND_COST: Cannot be both free and charged ticket

  • INSUFFICIENT_PACKAGE: Need to upgrade package

  • INVALID_DELIVERY_METHOD: Delivery method not allowed for this organization

  • INVALID_EVENT: Event not qualified to have tickets

  • INVALID_EVENT_ID: Event ID must match ticket's event

  • INVALID_INVENTORY_TIER_ID: Cannot change inventory tier of ticket

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
costNoCost (CURRENCY,cents)
freeNoIs free
nameNoTicket name
hiddenNoIs hidden
donationNoIs donation
event_idYesEvent ID (required)
auto_hideNoAuto-hide when not on sale
sales_endNoSales end (ISO 8601)
descriptionNoTicket description
include_feeNoInclude fee in price
sales_startNoSales start (ISO 8601)
quantity_totalNoTotal available
auto_hide_afterNoAuto-hide after time
hide_sale_datesNoHide sale dates
ticket_class_idYesTicket Class ID (required)
auto_hide_beforeNoAuto-hide before time
delivery_methodsNoDelivery methods
hide_descriptionNoHide description
maximum_quantityNoMax per order
minimum_quantityNoMin per order
inventory_tier_idNoInventory tier ID
sales_start_afterNoTrigger ticket ID
order_confirmation_messageNoConfirmation message
secondary_assignment_enabledNoSecondary barcode enabled

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.1/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 well: it discloses partial-update semantics, a time-gated field requirement, mutual-exclusion rules (include_fee vs split_fee, donation vs cost/free), and a detailed 400-error catalog that reveals validation constraints. It does not describe the response body or reversibility, keeping it out of the top band.

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?

Front-loaded with purpose, endpoint, and partial-update rule, then organized into clearly labeled sections (public fields, private fields, errors, auth). It is long, but the 24-parameter surface justifies much of it, though the field list partially restates schema descriptions and the error catalog is verbose.

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?

For a mutation tool with no annotations and no output schema, the description covers endpoint, auth, update semantics, all editable fields, and the error taxonomy. The main gap is the absence of any statement about the return value, which matters since no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: the exact cost format ('CURRENCY,amount_in_cents'), the allowed delivery_methods values, the public/private field grouping, and mutual-exclusion constraints. These exceed the terse one-line schema descriptions.

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: 'Update an existing Ticket Class for an event,' and pins it to an exact endpoint (POST /events/{event_id}/ticket_classes/{ticket_class_id}/). This distinguishes it from siblings like create_ticket_class, get_ticket_class, and list_ticket_classes without opening any schema.

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?

Provides useful operating constraints ('Supports partial updates', inventory_tier_id required after May 7 2020 for tiered events) that shape when it can be used, but never names alternatives or states when-not-to-use this tool. Usage is implied through the field/constraint notes rather than explicitly articulated.

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