eventbrite-mcp

create_webhook

Register a webhook endpoint for an Eventbrite organization to receive notifications when specified actions occur, optionally scoped to a single event.

Instructions

Create a Webhook by Organization ID.

ENDPOINT: POST /organizations/{organization_id}/webhooks/

Webhook represents webhook associated with Organization.

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": {
      "organization_id": "<organization_id>",
      "endpoint_url": "<endpoint_url>",
      "actions": "<actions>"
    },
    "name": "create_webhook"
  }
}

Input Schema

Name	Required	Description
`actions`	Yes	Actions to trigger webhook (required)
`event_id`	No	Event ID to scope webhook
`endpoint_url`	Yes	Webhook endpoint URL (required)
`organization_id`	Yes	Organization ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Sep 13, 2026

TDQS

B3.1/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 usefully discloses the required Bearer token auth and the exact HTTP endpoint, which an agent cannot derive from the schema alone. However, it omits mutation-relevant behavior: what happens on duplicate endpoint_url, what the created object returns, or any 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.

Conciseness3/5

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

Front-loaded with the action and endpoint, and the auth block is scannable. However, the sentence 'Webhook represents webhook associated with Organization' is tautological filler that adds nothing an agent can act on.

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?

The description supplies auth and endpoint context, which is valuable for a tool with no annotations and no output schema. It is still thin for a mutation tool: no note on the return payload, duplicate handling, or validation constraints on the actions array.

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%, so the schema already documents all four parameters including which are required. The description only references organization_id and adds no semantics for actions, event_id, or endpoint_url, so baseline 3 is appropriate.

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 a Webhook') and scopes it to an Organization ID, distinguishing it from the sibling read/create variants like list_webhooks and delete_webhook. It stops short of explicitly naming those siblings as alternatives, but the operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says nothing about when to create a webhook versus other options, nor any prerequisites (e.g., whether the organization must already have webhook capacity, or how this relates to delete_webhook/update variants). The only guidance is the auth requirement.

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

Deploy Server