Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_event_description

Fetch an Eventbrite event's full HTML description by event ID to display complete event details for New and Classic Create events.

Instructions

Retrieve full HTML description for an Event.

ENDPOINT: GET /events/{event_id}/description/

Returns fully rendered description as HTML string. Works with events created using New or Classic Create.

PERMISSIONS: event.details:read

ERRORS (400):

  • NOT_AUTHORIZED: No permission to view details

  • ARGUMENTS_ERROR: Invalid event ID

AUTHENTICATION: Requires: Authorization: Bearer PERSONAL_OAUTH_TOKEN

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "get_event_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: it documents the HTTP endpoint, the exact permission required (event.details:read), specific error codes with meanings, and the authentication scheme (Bearer PERSONAL_OAUTH_TOKEN). This is rich behavioral context well beyond what structured fields supply.

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?

Front-loaded with the core purpose, then organized into labeled sections (ENDPOINT, PERMISSIONS, ERRORS, AUTHENTICATION) that make scanning efficient. Slightly verbose with its multi-section format, but every section is useful for correct invocation.

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

Completeness5/5

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

Given a single simple parameter, no output schema, and no annotations, the description is complete: it covers purpose, endpoint, return format, permissions, errors, and auth. An agent has everything needed to call it correctly.

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 coverage is 100% (event_id is documented as 'Event ID (required)'), so the baseline is 3. The description adds the endpoint path showing event_id is a path parameter, but no additional syntax or constraints beyond that.

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 and resource: 'Retrieve full HTML description for an Event.' Clearly distinguishes from siblings like get_event, get_structured_content, and get_text_overrides by naming the exact sub-resource (description) and return format (HTML).

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?

Mentions it 'Works with events created using New or Classic Create,' implying a compatibility condition, but offers no explicit when-to-use-vs-alternatives guidance. An agent must infer that this is the tool for fetching description content as opposed to metadata (get_event) or structured content (get_structured_content).

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