Skip to main content
Glama
chrischall

eventbrite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

eb_org_ticket_groups

Read-only

List an organization's ticket groups (bundled ticket classes across events) by supplying its org ID. Supports pagination and compact or full response views.

Instructions

List an organization's ticket groups (ticket classes bundled across events).

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)
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

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the 'bundled across events' context and the view parameter's behavioral detail (compact strips image/avatar URLs, full returns Eventbrite's payload untouched). It doesn't disclose pagination behavior or rate limits, but the readOnly annotation covers the main safety profile.

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?

The description is a single clear sentence that front-loads the main purpose. The parenthetical adds useful disambiguation without bloat. The schema's view parameter description is verbose but earns its place by explaining the compact/full distinction and the rationale for not offering field projection.

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 a simple read-only list tool with 100% schema coverage and a readOnlyHint annotation, the description is mostly adequate. However, it doesn't mention pagination behavior (the continuation parameter implies it), what fields the response contains, or how this relates to eb_ticket_classes. An agent might not know whether to call this or eb_ticket_classes without more explicit guidance.

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 100%, so the schema already documents all three parameters. The description adds minimal extra meaning beyond the schema: it clarifies that org_id comes from eb_my_organizations and that view controls response shape. The view parameter's description is unusually detailed and helpful, but the tool description itself doesn't add much beyond what the schema provides.

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 states a specific verb ('List') and resource ('an organization's ticket groups'), with a clarifying parenthetical that ticket groups are ticket classes bundled across events. This distinguishes it from eb_ticket_classes (which lists ticket classes for an event) and eb_org_events, though it doesn't explicitly name a sibling.

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 the tool is for listing ticket groups at the organization level, and the org_id parameter description ('from eb_my_organizations') gives a hint about where the ID comes from. However, it doesn't explicitly state when to use this over eb_ticket_classes or other sibling tools, nor does it mention pagination usage beyond the continuation parameter.

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