Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

unpublish_event

Unpublish an Eventbrite event by ID to remove it from public view when sales and series rules allow. Returns true if successful.

Instructions

Unpublish an Event.

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

Returns boolean indicating success or failure of unpublish action.

UNPUBLISH REQUIREMENTS:

  • Free Event (including past): Must not have pending or completed orders

  • Paid Event (completed/paid out): Can be unpublished

  • Paid Event (not completed): Can only unpublish if no pending or completed orders

SERIES PARENT EVENTS:

  • All occurrences must be in valid state to unpublish

  • Unpublishing parent unpublishes all occurrences

  • Series occurrence cannot be unpublished individually

RESPONSE:

  • unpublished (boolean): true if successfully unpublished

POSSIBLE ERRORS (400):

  • NOT_PUBLISHED: Event not currently published, cannot unpublish

  • CANNOT_UNPUBLISH: Cannot unpublish event with pending/completed sales (unless past/completed/paid out for paid tickets), or if series parent has occurrences in invalid state, or if trying to unpublish individual series occurrence

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: it discloses the auth requirement (Bearer PERSONAL_OAUTH_TOKEN), the boolean return shape, the cascade behavior (unpublishing a parent unpublishes all occurrences), and specific 400 error codes with their meanings. This is unusually thorough behavioral disclosure.

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?

Headers segment the content well and the purpose is front-loaded, but the error section partially re-states the unpublish requirements already listed above, adding some redundancy. Still appropriately sized for the number of edge cases.

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?

Without an output schema, the description compensates by describing the return value and enumerating failure modes, plus auth and series interactions. An agent has everything needed to call this correctly and interpret the result.

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% for the single event_id parameter and the description adds no format or syntax detail beyond its use in the endpoint path. Baseline 3 applies when the schema already documents the parameter fully.

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 ('Unpublish an Event') plus the exact endpoint POST /events/{event_id}/unpublish/, making it trivially distinguishable from the inverse sibling publish_event. Nothing about the core action is left ambiguous.

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?

The UNPUBLISH REQUIREMENTS block gives explicit per-state conditions (free/paid/completed) and the SERIES PARENT EVENTS block explains when the action is prohibited, which is strong when/when-not guidance. It stops short of naming alternatives such as cancel_event or delete_event, so a 4 rather than 5.

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