Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_event_schedule

Creates a recurring Eventbrite event schedule for a series parent by adding occurrences from an iCalendar recurrence rule and duration.

Instructions

Create an event schedule for series parent.

ENDPOINT: POST /events/{event_id}/schedules/

Adds occurrences to series parent according to pattern. Requires series parent event.

PARAMETERS:

  • occurrence_duration: Duration in seconds

  • recurrence_rule: iCalendar RFC format with DTSTART

ERRORS (400):

  • MISSING, INVALID, DTSTART_MISSING, RECURRENCE_RULE_DATES_NOT_IN_UTC, DTSTART_OUTSIDE_PERMITTED_RANGE, LAST_OCCURRENCE_START_EXCEEDS_LIMIT, EXCEEDS_MAX_OCCURRENCES

ERRORS (403):

  • NOT_AUTHORIZED

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>",
      "occurrence_duration": "<occurrence_duration>",
      "recurrence_rule": "<recurrence_rule>"
    },
    "name": "create_event_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesSeries parent Event ID (required)
recurrence_ruleYesiCalendar recurrence rule (required)
occurrence_durationYesDuration in seconds (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the auth requirement (Bearer PERSONAL_OAUTH_TOKEN) and enumerates specific 400/403 failure modes (DTSTART_MISSING, RECURRENCE_RULE_DATES_NOT_IN_UTC, EXCEEDS_MAX_OCCURRENCES, NOT_AUTHORIZED). It omits idempotency, side effects on the parent, and rate limits.

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 one-line purpose and organizes the rest into labeled sections (endpoint, parameters, errors, auth), which is easy to scan. The PARAMETERS section largely duplicates the 100%-covered schema, so it earns its place only partially.

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 mutation tool with no annotations and no output schema, the description covers endpoint, auth, prerequisites, and error conditions, which is close to what an agent needs. It does not describe the return value or the effect on the parent event's existing schedule.

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%, so the schema already documents all three parameters, making 3 the baseline. The description restates occurrence_duration and recurrence_rule and adds only 'with DTSTART' as marginal extra meaning over the schema.

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?

States a specific verb and resource ('Create an event schedule for series parent') and clarifies it adds occurrences according to a recurrence pattern. Clearly distinguishable from sibling event tools, though it doesn't explicitly name the closest alternative (e.g. update_event).

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?

Provides a key prerequisite ('Requires series parent event') and scopes the operation to series parents, which implies when it applies. However, it gives no explicit when-to-use vs when-not guidance or comparison to sibling tools like update_event or create_event.

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