Skip to main content
Glama
chrischall

eventbrite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

eb_org_report

Read-only

Run an organization’s sales or attendees report to view aggregated event analytics, optionally filtered by date range, group, or event status.

Instructions

Run an organization's sales or attendees report — the aggregated analytics behind its events, optionally windowed by date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesWhich report to run
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)
end_dateNoISO date upper bound (YYYY-MM-DD)
group_byNoGrouping dimension, e.g. 'event', 'day', 'ticket_class'
start_dateNoISO date lower bound (YYYY-MM-DD)
continuationNoPagination continuation token from a previous response
event_statusNo

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description correctly frames this as a report operation with no side effects. It adds that the report is aggregated and optionally date-windowed, but it does not disclose pagination behavior, grouping effects, or response shape beyond what the schema's 'view' parameter already documents.

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, front-loaded sentence that communicates the core function and the key optionality. Every word earns its place, and it remains readable without unnecessary filler.

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

Completeness3/5

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

For an 8-parameter report tool with no output schema, the description is adequate but has gaps. It explains the high-level purpose and date windowing, and the schema covers most parameters, but it does not clarify what the report returns, how group_by affects rows, or how continuation tokens should be used across calls.

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 88%, so the schema carries most parameter meaning. The description reinforces the 'kind' values (sales or attendees) and the optional date window, but it does not add meaning beyond what the schema already provides for parameters like group_by, continuation, or event_status.

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?

The description clearly states a specific verb ('Run'), a resource ('an organization's sales or attendees report'), and the aggregated nature of the output. It does not explicitly name a sibling tool to differentiate from, but 'aggregated analytics behind its events' helps separate it from raw-list tools like eb_org_attendees or eb_org_orders.

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?

There is no explicit guidance on when to use this tool versus alternatives such as eb_org_attendees, eb_org_orders, or eb_org_events. The phrase 'aggregated analytics' implies a distinction from raw data tools, but no direct when-to-use or when-not-to-use guidance is 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