Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_webhooks

Retrieve all webhooks for an Eventbrite organization using its organization ID. Returns a paginated list to manage event notifications.

Instructions

List Webhooks by Organization ID.

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

Returns paginated response.

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>"
    },
    "name": "list_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idYesOrganization ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.6/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 disclose useful behavior: GET method, paginated response, and Bearer token authentication. It does not cover potential rate limits, error behavior, or detailed pagination mechanics beyond the fact that the response is paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Extremely concise and well-structured: purpose first, then endpoint, response behavior, and authentication. Every line is brief and relevant.

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 simple one-parameter list tool, the description supplies enough context to call it correctly: endpoint, required auth, and paginated return note. Without an output schema, it could say more about the returned webhook fields, but the missing detail is minor.

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 single parameter is already documented as required. The description repeats 'by Organization ID' and adds the endpoint path, but provides no additional semantic detail beyond what the schema supplies.

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 ('List Webhooks') plus a scoping constraint ('by Organization ID'). It is clearly distinguishable from create_webhook and delete_webhook, but it does not explicitly name those siblings or highlight the difference.

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?

Gives no when-to-use guidance, no conditions for choosing this tool over alternatives, and no exclusions. The endpoint and auth requirement are contextual details rather than usage guidance.

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