eventbrite-mcp

update_inventory_tier

Modify an existing Eventbrite inventory tier by ID, enabling partial updates to capacity, quantity, or name.

Instructions

Update an Inventory Tier by ID.

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

Supports partial updates.

ERRORS (400):

ARGUMENTS_ERROR
HOLD_QUANTITIES_EXCEEDS_CAPACITY_TOTAL: Sum of hold quantities must be less than capacity_total

ERRORS (403):

NOT_AUTHORIZED

ERRORS (404):

NOT_FOUND: Event or inventory_tier_id 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": "update_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
`inventory_tier_id`	Yes	Inventory Tier ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Sep 13, 2026

TDQS

B3.4/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 by disclosing the endpoint, partial update support, specific error codes (400 ARGUMENTS_ERROR, 400 HOLD_QUANTITIES_EXCEEDS_CAPACITY_TOTAL, 403 NOT_AUTHORIZED, 404 NOT_FOUND) and their meanings, plus auth requirements. It doesn't state whether updates are reversible or what the response looks like, but the error documentation is 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The error/auth block is well-organized and front-loaded with the core purpose first. However, the ENDPOINT line and error enumerations are somewhat verbose for what is a straightforward update operation, and the structured error list is closer to API reference material than agent guidance.

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 annotations and no output schema, the description covers auth, error handling, and update mode (partial). The main gap is lack of when-to-use guidance against siblings and no statement about return values or idempotency.

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 five parameters with descriptions. The description adds no parameter-specific meaning beyond what the schema provides. Baseline 3 is 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?

States a specific verb (update) and resource (Inventory Tier by ID), which distinguishes it from read siblings like get_inventory_tier. However, it doesn't differentiate from update_multiple_inventory_tiers or update_capacity_tier, which have overlapping purposes.

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 on when to use this tool versus update_multiple_inventory_tiers, create_inventory_tier, or update_capacity_tier. The description notes partial updates are supported but gives no context about when that's appropriate or when to prefer the batch sibling.

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

Deploy Server