Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_default_question

Fetches a default question's details from Eventbrite using event and question IDs for event registration.

Instructions

Retrieve a Default Question by ID.

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

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

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent ID (required)
question_idYesQuestion ID (required, e.g., "email")

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 so reasonably: it discloses the auth requirement (Bearer PERSONAL_OAUTH_TOKEN), the HTTP endpoint, and the 404/NOT_FOUND failure mode. The one notable gap is that the 404 is scoped only to 'Event doesn't exist' — it says nothing about a missing question_id.

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?

Front-loaded purpose followed by short labeled blocks (ENDPOINT, ERRORS, AUTHENTICATION). Every line is scannable and none is filler.

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?

There is no output schema, so the description is the only place to learn the return shape, yet it says nothing about what the retrieved question object contains. Errors and auth are covered, but the return-value gap is meaningful for a retrieval tool.

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 already documented, including the 'email' example for question_id. The description adds no format or constraint detail beyond the schema, so the baseline of 3 applies.

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?

The description states a specific verb and resource — 'Retrieve a Default Question by ID' — and the endpoint line confirms the target. It distinguishes itself from the create/update/delete/list default-question siblings, though it never explicitly contrasts with get_custom_question, leaving the 'default vs custom' distinction to inference.

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 only implied: it retrieves one question given an ID, so an agent can infer it is the single-item lookup counterpart to list_default_questions. There is no explicit when-to-use, no mention of when to prefer get_custom_question, and no prerequisite guidance beyond the auth note.

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