Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

eb_my_orders

Read-only

List the authenticated user's ticket orders with expanded event details, filter by upcoming or past events, and continue paginated results with tokens.

Instructions

List the authenticated user's ticket orders (attendee side), with the event expanded. time_filter narrows to upcoming or past events. view:"brief" answers one line per order — event name — start (local ISO) or "no date" — order status — inside the untrusted-data envelope, upcoming orders only unless time_filter says otherwise; a partial page ends with a "-- next: continuation=" note to pass back as continuation.

Input Schema

NameRequiredDescriptionDefault
viewNocompact (default) strips image/avatar URLs; "full" returns Eventbrite's payload untouched; "brief" returns one line per order: event name — start or "no date" — status (upcoming by default).
time_filterNoFilter orders by event time (default all; current_future under view:"brief")
continuationNoPagination continuation token from a previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / time_filter / description
      Previous value: -"Filter orders by event time (default all)"New value: +"Filter orders by event time (default all; current_future under view:\"brief\")"
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Eventbrite's payload untouched. No field projection on this tool: this server has no verified record of which Eventbrite fields matter here, and inventing one would risk dropping a field a caller needs."New value: +"compact (default) strips image/avatar URLs; \"full\" returns Eventbrite's payload untouched; \"brief\" returns one line per order: event name — start or \"no date\" — status (upcoming by default)."
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "compact",
-  "full"
-]New value: +[
+  "compact",
+  "full",
+  "brief"
+]
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Eventbrite's payload untouched. No field projection on this tool: this server has no verified record of which Eventbrite fields matter here, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds much more: results arrive inside an untrusted-data envelope, brief mode silently defaults to upcoming-only, and a partial page appends a "-- next: continuation=<token>" note that must be passed back. These are non-obvious behaviors an agent would otherwise discover only by trial.

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-loads the core purpose, then layers filter and view behavior. It is a single dense sentence and the inline dash-separated brief format is a bit hard to parse, but almost every clause carries operational information and nothing is redundant filler.

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?

There is no output schema, so the description carries the return-value burden; it handles brief mode, the untrusted-data envelope, and pagination. It does not describe what compact or full responses look like beyond the schema's own notes, which is a minor gap for a read-only list tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it explains how the continuation token is surfaced in output and fed back, and how view:"brief" changes filtering behavior in a way the enum description only hints at. That goes beyond restating the schema.

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 and resource ("List the authenticated user's ticket orders") and pins the perspective with "(attendee side)", which separates it from organizer-scoped siblings like eb_org_orders and eb_event_orders. An agent can route between attendee and organizer order tools without opening a 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?

Gives actionable conditions: time_filter narrows to upcoming or past, and view:"brief" is described as one line per order with an upcoming-only default unless time_filter overrides. It stops short of explicit exclusions (e.g., "use eb_org_orders for organization-level orders"), so usage context is clear but alternatives are only implied by "attendee side".

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