Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_inventory_tier

Remove a specific inventory tier from an Eventbrite event when it has no attendees, seat assignments, or active ticket dependencies.

Instructions

Delete an Inventory Tier.

ENDPOINT: DELETE /events/{event_id}/inventory_tiers/{inventory_tier_id}/

ERRORS (400):

  • HAS_ATTENDEES: Cannot delete if purchased by attendees

  • IS_STARTED_AFTER: Another ticket starts when this ends

  • LAST_TICKET: Cannot delete last ticket while event live

  • HAS_SEAT_ASSIGNMENTS: Cannot delete if seats still assigned

ERRORS (403):

  • NOT_AUTHORIZED

ERRORS (404):

  • NOT_FOUND: Event or tier doesn't exist

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>",
      "inventory_tier_id": "<inventory_tier_id>"
    },
    "name": "delete_inventory_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent ID (required)
inventory_tier_idYesInventory Tier ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.7/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 behavioral burden and does so excellently: it lists the exact endpoint, authentication requirement, and detailed error conditions (HAS_ATTENDEES, IS_STARTED_AFTER, LAST_TICKET, HAS_SEAT_ASSIGNMENTS, NOT_AUTHORIZED, NOT_FOUND) that reveal critical prerequisites and restrictions. This is far beyond what a simple delete description usually provides.

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?

The description is front-loaded with the core action and structured with clear headers for endpoint, errors, and authentication. The endpoint line is slightly redundant, but the bulleted error list is efficient and information-dense.

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 delete tool with no output schema, the description covers authentication and specific failure conditions well. It does not explicitly state irreversibility or success behavior, but these are largely implied by the operation itself and the absence of an output schema.

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 both required parameters, so the schema already documents them. The description adds no additional meaning about parameter format or constraints, making the baseline 3 appropriate.

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?

The description states a specific verb ("Delete") and resource ("Inventory Tier"), making the operation unambiguous. It does not explicitly differentiate itself from sibling tools like update_inventory_tier or get_inventory_tier, but the verb alone is sufficient for an agent to distinguish it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as when to delete versus archive or update a tier. The error conditions hint at constraints, but they describe failure modes rather than usage guidelines.

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