Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cancel_event

Cancel an Eventbrite event by ID, provided it has no pending or completed orders. For series events, cancelling the parent cancels all occurrences.

Instructions

Cancel an Event.

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

Returns boolean indicating success or failure.

CANCEL REQUIREMENTS:

  • Event must not have pending or completed orders

SERIES PARENT EVENTS:

  • All occurrences must be in valid state to cancel

  • Canceling parent cancels all occurrences

RESPONSE:

  • canceled (boolean): true if successfully canceled

POSSIBLE ERRORS (400):

  • ALREADY_CANCELED: Event already canceled

  • CANNOT_CANCEL: Event has pending/completed ticket sales that must be refunded first, or series parent has occurrences that cannot be canceled

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "cancel_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.7/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 series-parent side effect (canceling a parent cancels all occurrences), the order-state precondition, the 400 error codes, the boolean return, and the required Bearer OAuth token. The one notable gap is whether a cancellation is reversible.

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?

Labeled sections (REQUIREMENTS, SERIES PARENT EVENTS, RESPONSE, ERRORS, AUTHENTICATION) make it skimmable and the critical 'Cancel an Event' purpose is front-loaded. Minor redundancy: 'Returns boolean indicating success or failure' is restated by the RESPONSE block.

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 single-parameter mutation with no output schema and no annotations, the description covers preconditions, cascading series behavior, error modes, and auth. Only the reversibility/idempotency question remains unanswered, which is a modest gap.

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 event_id parameter, so the schema already documents it fully; the description only conveys it indirectly via the endpoint path. Baseline 3 applies when the schema does the heavy lifting.

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 ('Cancel an Event') and pins the API endpoint, which is unambiguous on its own. However, it does not distinguish itself from the sibling delete_event, leaving an agent to infer whether cancel and delete differ.

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?

The 'CANCEL REQUIREMENTS' and 'POSSIBLE ERRORS' sections imply the preconditions for use (no pending/completed orders), which is useful context. But there is no explicit statement of when to choose cancel_event over delete_event or unpublish_event, so routing guidance is only implied.

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