Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_multiple_inventory_tiers

Create multiple inventory tiers in a single request to reduce API calls and simplify event ticket setup.

Instructions

Create Multiple Inventory Tiers (Bulk)

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

Creates multiple inventory tiers in a single request for efficient bulk operations.

Authentication: Requires a valid Eventbrite API token with event management permissions.

Use Cases:

  • Set up multiple inventory tiers at once during event creation

  • Bulk import inventory tier configurations

  • Efficiently configure complex inventory structures

  • Reduce API calls when setting up many tiers

Inventory Tier Fields:

  • name: Tier name (required)

  • quantity: Number of tickets in this tier

  • price: Price for this tier (if applicable)

  • sales_start: When sales begin for this tier

  • sales_end: When sales end for this tier

  • minimum_quantity: Minimum tickets per order

  • maximum_quantity: Maximum tickets per order

Limits:

  • Maximum 100 inventory tiers per event

  • All tiers must belong to the same event

Error Codes:

  • 400: Invalid tier data or exceeds maximum tiers

  • 401: Authentication required

  • 403: Insufficient permissions

  • 404: Event not found

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesThe event ID to create inventory tiers for
inventory_tiersYesArray of inventory tier objects to create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4/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 well: it declares the required auth scope (event management permissions), the 100-tier per-event limit, the same-event constraint, and the 400/401/403/404 error semantics. It stops short of covering idempotency or rate limiting.

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?

Front-loads the core action and endpoint, but the markdown scaffolding (four headers, a field list duplicating the schema, four error codes) makes it longer than necessary. Meaningful content is diluted by restatement.

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 mutation tool with no output schema and no annotations, the description supplies the essentials an agent needs: auth, hard limits, and failure modes. Only the response shape and pagination/batching behavior remain unaddressed.

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 baseline is 3. The field list (name, quantity, price, sales_start/end, min/max quantity) largely restates what the schema already exposes, adding only the note that name is required, so it does not materially extend parameter understanding.

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 (create) and resource (multiple inventory tiers) plus the endpoint and the bulk scope, which distinguishes it from the singular create_inventory_tier and update_multiple_inventory_tiers siblings. An agent can identify the operation without opening the schema.

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?

Four explicit use cases (bulk setup, import, complex configs, reducing API calls) give clear context for when to reach for this tool. It does not, however, name the alternative (create_inventory_tier for a single tier) or state when not to use the bulk endpoint.

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