Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

eb_event_details

Read-only

Batch-fetch public Eventbrite event details by numeric ID, using a bearer token or browser bridge when no token is configured.

Instructions

Batch-fetch public event details by id. Uses your bearer token by default, falling back to the browser bridge when no token is configured. For ticket-class detail prefer eb_ticket_classes.

Input 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.
expandNoComma-separated expansions (default primary_venue,image,ticket_availability,event_sales_status,primary_organizer)
event_idsYesNumeric event ids (the digits at the end of an event URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • changedInput schema / properties / event_ids / description
      Previous value: -"Numeric event ids"New value: +"Numeric event ids (the digits at the end of an event URL)"
    • addedInput schema / properties / event_ids / items / pattern
      Added value: +"^\\d+$"
  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.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared by annotations, the description adds genuinely useful behavioral context absent from structured data: the bearer-token default and the browser-bridge fallback when no token exists. It stops short of disclosing rate limits, pagination, or error behavior for a batch endpoint capped at 20 ids.

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?

Three tight sentences, each earning its place: purpose and scope front-loaded, then the auth behavior, then the alternative routing. 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 batch tool with no output schema and full schema coverage, the description covers purpose, auth fallback, and sibling routing adequately. It leaves minor gaps around batch semantics (ordering, partial-failure behavior) but nothing that would block correct invocation.

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% – event_ids, expand, and the compact/full view enum are all thoroughly documented in the schema itself. The description only echoes "by id" and adds no format or syntax details beyond the schema, so the baseline 3 applies.

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?

"Batch-fetch public event details by id" states a specific verb (batch-fetch), resource (public event details), and access pattern (by id). The word "batch" implicitly distinguishes it from the singular eb_event sibling, and it explicitly routes ticket-class lookups to eb_ticket_classes. It does not, however, clarify how it relates to eb_event or eb_event_description.

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?

It gives an explicit alternative for one case ("For ticket-class detail prefer eb_ticket_classes") and the "batch" framing implies the multi-id use case. There is no explicit when-not guidance versus eb_event or eb_event_description, so it falls short of full alternative coverage.

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