Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_default_question

Deactivate a canned question on an Eventbrite event by deleting its default question ID, so it no longer appears in event registration.

Instructions

Delete Default Question by ID.

ENDPOINT: DELETE /events/{event_id}/canned_questions/{question_id}/

Deactivates canned question for event.

ERRORS (404):

  • NOT_FOUND: Event doesn't exist

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

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent ID (required)
question_idYesQuestion ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4/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 discloses important behavior: the operation is a soft delete (deactivates rather than permanently removes), it requires a Bearer token, and it returns 404 if the event doesn't exist. It does not state what happens if the question itself is missing or whether the question remains retrievable, leaving some gaps.

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?

The description is front-loaded with the core purpose, then structured into endpoint, behavior note, errors, and authentication. Every line adds useful operational detail with no redundant 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 two-parameter delete tool with no output schema or annotations, the description covers the endpoint, soft-delete behavior, error case, and authentication requirement. It is nearly complete, though the omission of handling for a missing question (vs. missing event) and any response details leaves a minor gap.

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 both parameters are fully documented in the schema. The description adds no syntax, format, or meaning beyond what the schema already provides.

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?

The description states a specific verb (Delete) and resource (Default Question) and clarifies the operation is a deactivation of a canned question. This distinguishes it from sibling tools like delete_custom_question and update_default_question.

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 name and the note that it deactivates a canned question, but there is no explicit when-to-use guidance, prerequisites, or named alternatives (e.g., update_default_question). An agent must infer the appropriate context.

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