Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_display_settings

Retrieve an event's display settings to control how it appears on Eventbrite listing pages. Provide the event ID and authenticate with a personal OAuth token.

Instructions

Retrieve Display Settings for an Event.

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

Display Settings control how Event appears on Event Listing page.

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_display_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the HTTP method and endpoint (GET /events/{event_id}/display_settings/) and the required authentication (Authorization: Bearer PERSONAL_OAUTH_TOKEN), which is genuinely useful behavioral context. However, it says nothing about error behavior, rate limiting, or what a missing event_id yields. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose in one sentence, then uses short labeled sections (ENDPOINT, AUTHENTICATION). No filler. Slightly unconventional for a tool description, but every line carries information.

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 one-parameter read tool with no output schema and no annotations, the description is roughly complete: it identifies the resource, endpoint, and auth. It omits any hint of what the response contains (e.g., name, color, layout fields) and any usage context relative to siblings.

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 there is a single required parameter already documented in the schema, so the baseline is 3. The description adds the endpoint path template which reinforces the param meaning, but does not add semantics beyond the schema.

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 (Retrieve) and resource (Display Settings for an Event), and clearly scopes them to how the Event appears on the Event Listing page. This distinguishes it from sibling update_display_settings and from other get_* entity tools.

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 a read operation for display settings but does not explicitly state when to use this tool versus update_display_settings or other event-related getters. Usage is inferable from the naming and the resource definition, but no explicit when/when-not guidance is given.

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