eventbrite-mcp

copy_event

Duplicate an existing Eventbrite event by ID to create a new event with a new ID, copying payment, payout, refund, and tax settings; optionally set new name and dates.

Instructions

Copy an Event, creating duplicate with new Event ID.

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

Creates new Event based on existing Event. Returns Event object for newly created Event.

COPIED ELEMENTS:

Event payment options
Payout method
Refund policy
Tax settings

POSSIBLE ERRORS (400):

INSUFFICIENT_PACKAGE: Need to upgrade package. Go to /users/{user_id}/assortment/
INVALID_END_DATE: End date must be 1 minute to 365 days after start time
INVALID_START_DATE: Start date must be between now and 10 years from now
UNABLE_TO_COPY_EVENT: Currently unable to copy. Recovery not possible
UNSUPPORTED_TIMEZONE: Timezone not supported

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": "copy_event"
  }
}

Input Schema

Name	Required	Description
`end`	No	End datetime (optional)
`name`	No	Name for copied event (optional)
`start`	No	Start datetime (optional)
`event_id`	Yes	Event ID to copy (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Sep 13, 2026

TDQS

A4.1/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 well: it enumerates the copied elements (payment options, payout method, refund policy, tax settings), lists concrete 400 error codes with meanings, notes auth via Bearer token, and states the return is the new Event object. It omits what is NOT copied (attendees, orders, ticket sales) and the initial state of the copy, which for a duplication tool is a notable gap.

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 first sentence, then clearly labeled sections (ENDPOINT, COPIED ELEMENTS, ERRORS, AUTHENTICATION). Slightly verbose with the raw endpoint path, but every block is scannable and useful; nothing is pure filler.

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 mutating tool with no annotations and no output schema, the description covers origin, effect, error modes, auth, and return shape. It is only short of describing what is left behind by the copy, which would help an agent predict side effects.

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 coverage is 100%, so the baseline is 3. However the error section adds real constraint semantics for the optional start/end parameters (end must be 1 minute to 365 days after start; start between now and 10 years out) that the schema does not express, so it earns above baseline.

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 ('Copy an Event, creating duplicate with new Event ID') and distinguishes itself from the many event-mutating siblings (create_event, update_event, delete_event). The first sentence alone tells an agent exactly what the tool produces.

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?

Usage is implied by the semantics of 'copy' versus 'create', but the description never states when to prefer this over create_event or update_event, nor what preconditions apply to the source event (e.g. must be unpublished). Adequate but inferential.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server