Skip to main content
Glama
chrischall

eventbrite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

eb_org_attendees

Read-only

List attendees across an organization's Eventbrite events, with optional status filter and pagination. Retrieve all attendee records from the organizer side for reporting or follow-up.

Instructions

List attendees across an organization's events (organizer side).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse 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.
org_idYesOrganization id (from eb_my_organizations)
statusNoAttendee status filter
continuationNoPagination continuation token from a previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
+}
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, so the description does not need to restate safety. It adds 'organizer side', which implicitly signals that organizer-level authorization is required, a useful behavioral note. However, it does not disclose other traits like pagination behavior or response shape beyond what the schema parameters (e.g., continuation, view) already explain. Given the annotation coverage, this is adequate but not rich.

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

Conciseness5/5

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

The description is a single, 8-word sentence that is front-loaded with the core action and scope. Every word earns its place: 'List' states the operation, 'attendees across an organization's events' specifies the resource and breadth, and '(organizer side)' adds access context. No filler or redundancy.

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 read-only list tool with a well-documented schema (100% parameter descriptions, enum explanations, continuation token) and readOnlyHint annotation, the description is sufficient. It clarifies the organizational scope and organizer context. It does not describe return values, but no output schema exists and the schema's pagination parameter implies a paginated list. Minor gap: it does not explicitly state that results aggregate across multiple events, though that is already in the description.

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?

The input schema has 100% description coverage, so all four parameters (view, org_id, status, continuation) are already documented. The description's phrase 'across an organization's events' reinforces the org_id scope but adds no new meaning beyond the schema's description for org_id (from eb_my_organizations). Baseline 3 is appropriate since the schema carries the semantic load.

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?

The description 'List attendees across an organization's events (organizer side)' uses a specific verb ('List'), a specific resource ('attendees across an organization's events'), and adds 'organizer side' to indicate the access context. This clearly distinguishes the tool from sibling tools like eb_event_attendees (single-event attendee list) and eb_event_attendee (single attendee), without needing to open their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for organizer-scoped, multi-event attendee listing but does not explicitly mention when to prefer this over alternatives such as eb_event_attendees. The 'organizer side' qualifier hints at the intended audience, and 'across an organization's events' clarifies scope, but no direct when-not or alternative references are given.

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