Skip to main content
Glama
prmichaelsen

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_discount

Retrieve an Eventbrite discount by ID to view its code, type, value, availability, and ticket or event restrictions.

Instructions

Retrieve a Discount by ID.

ENDPOINT: GET /discounts/{discount_id}/

DISCOUNT TYPES:

  • Public: Publicly displays on Event Listing/Checkout (single event only)

  • Coded: Requires secret code

  • Access Code: Secret code for hidden tickets (optional discount amount)

  • Hold: Unlock discount for seats on hold

DISCOUNT FIELDS:

  • code (string): Discount name (public) or code (coded/access)

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

  • end_date (datetime): Usable until this date (relative to event timezone)

  • end_date_relative (integer): Seconds before event start

  • amount_off (decimal): Fixed amount 0.01-99999.99 (uses event currency)

  • percent_off (decimal): Percentage 1.00-100.00

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

  • quantity_sold (integer, readonly): Times used

  • start_date (local datetime): Usable from this date

  • start_date_relative (integer): Seconds before event start

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

  • event_id (string): Single Event ID (empty for cross-event)

  • ticket_group_id (string): Ticket Group ID

  • hold_ids (list): Hold IDs this unlocks

EXPANSIONS:

  • event: Single Event for discount

  • ticket_group: Ticket Group for discount

  • reserved_seating: Reserved seating settings

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
discount_idYesDiscount ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses authentication requirements (Bearer token) and expands on discount types and fields, which is useful. However, it doesn't state read-only nature, error behavior (e.g., 404 for missing ID), or response format. For a retrieval tool with no annotations, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is bloated with extensive field lists, discount type explanations, and expansions that are tangential to the core retrieval action. The purpose statement is front-loaded, but the bulk is unnecessary for guiding invocation. Every sentence does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple retrieval tool with one parameter and no output schema, the description is overkill on field details but under-specifies crucial behavioral aspects like read-only status, error handling, and response structure. With no annotations, it should compensate more effectively for the missing structured metadata.

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 coverage is 100% for the single required parameter (discount_id), so the schema documents it fully. The description repeats 'Discount ID (required)' but adds no syntax or format details beyond the schema. Baseline 3 is appropriate when 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 clear verb (Retrieve) and resource (Discount by ID) and provides the exact endpoint. It distinguishes the resource from siblings like list_discounts and update_discount, though it doesn't explicitly name them. The core purpose is unmistakable.

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 list_discounts, create_discount, or update_discount. An agent is left to infer that this is for fetching a single known discount. No when-not-to-use or alternative routing is provided.

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