Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_discount

Create a new Eventbrite discount for an organization with public, coded, access, or hold types, set amount or percent off, and target events, ticket classes, or holds.

Instructions

Create a new Discount.

ENDPOINT: POST /organizations/{organization_id}/discounts/

DISCOUNT TYPES:

  • Public: Displays publicly (single event, no apostrophes/special chars except -_()/)

  • Coded: Secret code required (no spaces/apostrophes/special chars except -_()/)

  • Access Code: Secret code for hidden tickets (no spaces/apostrophes/special chars except -_()/)

  • Hold: Unlock seats on hold

DISCOUNT SCOPE:

  • event_id + ticket_class_ids: Specific tickets in single event

  • event_id only: All tickets in single event

  • ticket_group_id: Ticket Group discount

  • Neither: All tickets for all organization events (including future)

FIELDS:

  • code (string, required): Name (public) or code (coded/access)

  • type (string, required): access, coded, public, hold

  • amount_off (decimal): Fixed amount 0.01-99999.99 (event currency, 2 decimals)

  • percent_off (decimal): Percentage 1.00-100.00 (2 decimals)

  • quantity_available (integer): Usage limit (0 = unlimited)

  • start_date (local datetime): Usable from (empty = immediately)

  • start_date_relative (integer): Seconds before event start

  • end_date (datetime): Usable until (empty = event end_date)

  • end_date_relative (integer): Seconds before event start

  • ticket_class_ids (list): Ticket Class IDs (empty = all)

  • event_id (string): Single Event ID

  • ticket_group_id (string): Ticket Group ID

  • hold_ids (list): Hold IDs to unlock

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesDiscount code/name (required)
typeYesType: access, coded, public, hold (required)
end_dateNoEnd date (ISO 8601)
event_idNoEvent ID
hold_idsNoHold IDs
amount_offNoFixed amount off (decimal)
start_dateNoStart date (ISO 8601)
percent_offNoPercentage off (decimal)
organization_idYesOrganization ID (required)
ticket_group_idNoTicket Group ID
ticket_class_idsNoTicket Class IDs
quantity_availableNoUsage limit (0=unlimited)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.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 largely succeeds: it discloses the Bearer PERSONAL_OAUTH_TOKEN requirement, character restrictions per code type, numeric ranges, and default semantics (empty date = immediately, empty end_date = event end_date, 0 = unlimited). It does not describe the creation side effects or response payload, which is a modest gap.

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?

Front-loaded with the one-line purpose, then cleanly partitioned under ENDPOINT, DISCOUNT TYPES, DISCOUNT SCOPE, FIELDS and AUTHENTICATION headings. It is long, but the length is justified by a 12-parameter mutation; some field text restates schema descriptions with little added value.

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 12-param mutation with no annotations and no output schema, the description supplies the endpoint, auth, type/scope combinatorics and field defaults that an agent needs to call it correctly. The main omission is any statement of what the call returns (e.g., created discount ID) and confirmation of non-reversible creation, which would complete the picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100% (baseline 3), the description adds substantial meaning the schema lacks: numeric ranges for amount_off (0.01-99999.99) and percent_off (1.00-100.00), the 2-decimal/event-currency constraint, the '0 = unlimited' and 'empty = all/immediately' defaults, and the interaction rules that decide scope from which of event_id/ticket_class_ids/ticket_group_id are supplied.

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+resource ('Create a new Discount') and immediately disambiguates from siblings get_discount/update_discount/list_discounts/delete_discount by detailing the discount taxonomy (public/coded/access/hold) and scope rules. An agent can tell exactly what this tool produces 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?

The DISCOUNT TYPES and DISCOUNT SCOPE sections effectively tell the agent how to combine event_id, ticket_class_ids and ticket_group_id for each intent, and the AUTHENTICATION block names the required token. It stops short of explicit 'use this instead of X' routing, but the deployment guidance is rich.

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