Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

publish_event

Publishes an Eventbrite event or series parent after validating required details and payment options. Returns a boolean success result.

Instructions

Publish an Event.

ENDPOINT: POST /events/{event_id}/publish/

In order for publish to be permitted, the event must have all necessary information, including a name and description, an organizer, at least one ticket, and valid payment options. This API endpoint will return argument errors for event fields that fail to validate the publish requirements. Returns a boolean indicating success or failure of the publish.

If the event is a series parent, all occurrences in the series must be in a valid state to be published. Publishing the series parent will publish all series occurrences.

Deleted Events cannot be published.

REQUIREMENTS FOR PUBLISHING:

  • Event must have a name

  • Event must have a description or summary

  • Event must have an organizer

  • Event must have at least one ticket class

  • If event has paid tickets, must have valid payment options configured:

    • Payment country must be set

    • Payment type must be configured

    • If using PayPal, PayPal email must be specified

    • Split fees are not supported (deprecated)

SERIES PARENT EVENTS:

  • All occurrences must be in valid state

  • Publishing parent publishes all occurrences

  • Must have at least one date scheduled

RESPONSE: Returns object with:

  • published (boolean): true if successfully published

POSSIBLE ERRORS (400):

  • ALREADY_PUBLISHED_OR_DELETED: Event already published or deleted

  • NO_PAYMENT_OPTIONS: Event has paid tickets but no payment options configured

  • PAYMENT_OPTIONS_DEPRECATED_SPLIT_FEES: Split fees configured (no longer supported)

  • PAYMENT_OPTIONS_NO_COUNTRY: Paid tickets but no payment country configured

  • PAYMENT_OPTIONS_NO_PAYMENT_TYPE: Paid tickets but no payment type configured

  • PAYMENT_OPTIONS_PAYPAL_NO_EMAIL: PayPal configured but no email specified

  • PUBLISH_FREE_EVENT_FEATURE_DENIED: Reached limit of free events in Professional plan

  • ERROR_CANNOT_PUBLISH_SERIES_WITH_NO_DATES: Series must have at least one date scheduled

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEvent ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.4/5.0
Behavior5/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 thoroughly: it discloses the auth requirement (Bearer token), the mutation semantics, the series-propagation side effect (publishing a parent publishes all occurrences), the boolean success response, and a full enumerated error taxonomy with codes and causes. This is substantially more than a bare 'publishes an event'.

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?

Well-structured with labeled sections (REQUIREMENTS, SERIES PARENT, RESPONSE, ERRORS, AUTH) and front-loaded with the endpoint and intent. However, the publish requirements are partially duplicated between the narrative paragraph and the bulleted REQUIREMENTS list, which is mild redundancy.

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?

For a single-param mutation tool with no output schema, the description covers prerequisites, side effects on series, error conditions, response shape, and authentication. Nothing an agent needs to invoke it correctly is missing.

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?

Only one parameter (event_id) with 100% schema description coverage, so the baseline is 3. The description mentions event_id only implicitly through the endpoint path and adds no format, type, or sourcing detail beyond the schema.

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+resource ('Publish an Event') and gives the exact endpoint (POST /events/{event_id}/publish/). It is trivially distinguishable from the sibling unpublish_event, so an agent can route correctly 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 Guidelines4/5

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

Provides a rich when-permitted context: all validation requirements, series-parent semantics, and the fact that deleted events cannot be published. It does not explicitly name unpublish_event as the inverse alternative, so it stops short of full alternative routing, but the usage conditions are otherwise explicit.

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