eventbrite-mcp

create_inventory_tier

Create a new Inventory Tier for an Eventbrite event to define ticket capacity and quantity. Add up to 100 tiers per event via POST /events/{event_id}/inventory_tiers/.

Instructions

Create a new Inventory Tier for an Event.

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

Max 100 tiers per event.

ERRORS (400):

EXCEED_MAXIMUM_INVENTORY_TIERS: Cannot create more than 100 tiers
EXCEED_MAXIMUM_TICKET_RULE_TICKETS: Ticket rule tickets cannot exceed 1000
ARGUMENTS_ERROR

ERRORS (403):

NOT_AUTHORIZED

ERRORS (404):

NOT_FOUND: Event 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>"
    },
    "name": "create_inventory_tier"
  }
}

Input Schema

Name	Required	Description
`name`	No	Tier name
`event_id`	Yes	Event ID (required)
`capacity_total`	No	Total capacity
`quantity_total`	No	Total quantity

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Sep 13, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations present, the description carries the full burden and does it well: it discloses the max-of-100 constraint, the 1000 ticket-rule limit, the exact 400/403/404 error codes, and the required Bearer auth scheme. It falls short of describing the response shape or how capacity_total and quantity_total relate, but the operational constraints are unusually thorough.

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 purpose sentence is front-loaded, followed by cleanly labeled ENDPOINT, ERRORS, and AUTHENTICATION blocks. The verbatim error dump is slightly heavy, but each block maps to information an agent actually needs before calling.

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 creation tool with no annotations and no output schema, the description supplies auth, endpoint, quota limits, and failure modes. The main gap is the absence of any indication of what a successful response contains, which the agent has to discover empirically.

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%, so the schema already documents all four parameters, and the description adds essentially no additional parameter-level meaning. Baseline 3 is appropriate 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 ('Create a new Inventory Tier for an Event') and pins the endpoint, so an agent knows exactly what operation this performs. It does not explicitly contrast itself with the sibling create_multiple_inventory_tiers, but the singular phrasing makes the distinction inferable.

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 statement of when to prefer this tool over its obvious alternative, create_multiple_inventory_tiers, or over update_inventory_tier. The 100-tier cap gives a hint about batching, but the agent must infer the single-vs-bulk routing decision on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server