Skip to main content
Glama
chrischall

eventbrite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

eb_venue

Read-only

Retrieve venue details (name, address, geo) by venue ID from Eventbrite. Useful for resolving venue information from event or organizer data.

Instructions

Get a venue by id (name, address, geo). Venue ids appear on expanded events and in eb_org_venues.

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.
venue_idYesNumeric venue id

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.2/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, and the description's 'Get' is consistent with that. The description adds minimal behavioral context (returns name, address, geo) but does not disclose error behavior, auth requirements, or rate limits. Since the safety profile is covered by annotations, 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 sentences, no filler. The core action and resource are front-loaded, and the follow-up sentence provides a useful pointer without digressing. Every word earns its place.

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 simple ID-lookup tool with no output schema, the description offers a high-level summary of the return fields (name, address, geo) and where to find IDs. It does not cover error handling or edge cases, but given the schema's thorough description of the view parameter and the tool's simple nature, it is nearly complete. A short example or mention of error behavior would push it to 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining where a venue_id comes from ('on expanded events and in eb_org_venues'), which helps the agent understand and source the required parameter. The view parameter is fully explained in the schema, so the description's addition is focused and useful.

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 states a specific verb and resource: 'Get a venue by id (name, address, geo).' It clearly distinguishes this from sibling eb_org_venues (which lists venues) by focusing on fetching a single venue by ID, and it even tells the agent where venue IDs are found (expanded events and eb_org_venues).

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 description implies when to use it: when you have a venue ID it directs you to the sources of those IDs ('Venue ids appear on expanded events and in eb_org_venues'). It does not explicitly name alternatives like eb_venue_events or state when not to use it, but the context is clear enough for an agent to select this tool for a single-venue lookup.

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