Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_event

Permanently delete an Eventbrite event or series parent when it has no pending or completed orders, removing all associated occurrences.

Instructions

Delete an Event if the delete is permitted.

ENDPOINT: DELETE /events/{event_id}/

Returns a boolean indicating the success or failure of the delete action.

To delete an Event, the Event must not have any pending or completed orders.

If the event is a series parent, all series occurrences must be in a valid state to be deleted. Deleting the series parent will delete all series occurrences.

WARNING: This action cannot be undone. Deleted events cannot be recovered.

DELETION REQUIREMENTS:

  • Event must not have any pending orders

  • Event must not have any completed orders

  • For series parents: all occurrences must meet deletion requirements

SERIES PARENT EVENTS:

  • All occurrences must be in valid state for deletion

  • Deleting parent deletes all occurrences

  • Cannot delete if any occurrence has pending/completed orders

RESPONSE: Returns object with:

  • deleted (boolean): true if successfully deleted

POSSIBLE ERRORS (400):

  • ALREADY_DELETED: Event has already been deleted

  • CANNOT_DELETE: Cannot delete event that has pending or completed orders, or series parent where any occurrence has pending or completed orders

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.1/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so thoroughly. It discloses destructive irreversibility, authentication requirements, return value, possible errors, and series-wide deletion 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?

The description is front-loaded with a warning and uses headings for structure, which helps scanning. However, the same deletion requirements and series constraints are repeated across multiple sections, making it longer than necessary.

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 destructive deletion tool with no output schema and only one input parameter, the description covers return shape, possible errors, authentication, preconditions, and series-parent consequences. An agent has enough information to invoke it safely and interpret results.

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% and the single required event_id parameter is already documented in the schema. The description adds no extra syntax, format, or semantic detail beyond what the schema provides, so the baseline 3 applies.

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 and resource ('Delete an Event') with clear scope, but does not name or distinguish sibling alternatives such as cancel_event or unpublish_event. An agent can identify the action, though not why it would choose this over related tools.

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 explicit preconditions for when deletion is permitted, including no pending/completed orders and valid series occurrence states. It does not compare alternatives or explicitly say when not to use this tool versus cancel_event, but the conditional context is clear.

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