Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

eb_reference

Read-only

List Eventbrite categories, subcategories, formats, timezones, countries, or regions to retrieve IDs for event search filters.

Instructions

List Eventbrite reference data: categories (103=Music, 101=Business, 110=Food & Drink, …), subcategories, formats, timezones, countries or regions. Category/subcategory/format ids feed eb_search_events filters.

Input Schema

NameRequiredDescriptionDefault
kindYesWhich list to fetch
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.

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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe external read. The description adds that the output is reference data whose ids are inputs elsewhere, but says nothing about caching, volatility of the lists, or rate limits. With the safety profile already covered, 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?

Two dense sentences with zero filler; the resource list comes first and the consumer relationship second, so the most useful information is front-loaded.

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 enumeration tool with no output schema, the description tells the agent what lists exist and why the ids matter, which is enough to call it correctly. It could say more about the shape/size of each list, but the schema's view parameter partially covers that.

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% and the 'view' parameter already carries an unusually detailed explanation of compact vs full, so the schema does the heavy lifting. The description's category examples (103=Music, 101=Business) hint at what 'kind' returns but add no syntax or format detail for either parameter; baseline 3 applies.

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 (List) and resource (Eventbrite reference data) and enumerates the exact resource families, mirroring the schema enum. It also distinguishes itself from siblings by naming eb_search_events as the consumer of the returned ids, so an agent can route without opening either 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?

The sentence 'Category/subcategory/format ids feed eb_search_events filters' gives a clear reason to call this tool (harvesting ids before a search). It stops short of explicit when-not guidance or naming alternatives for the timezone/country/region lists, so it is strong context but not full routing.

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