Skip to main content
Glama
Sign In
eventbrite-mcp

eventbrite-mcp

by prmichaelsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_subcategory

Retrieve a Subcategory by ID from the Eventbrite API to fetch official category details for events.

Instructions

Retrieve a Subcategory by ID.

ENDPOINT: GET /subcategories/{subcategory_id}/

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": {
      "subcategory_id": "<subcategory_id>"
    },
    "name": "get_subcategory"
  }
}

Input Schema

NameRequiredDescriptionDefault
subcategory_idYesSubcategory ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose the concrete endpoint (GET /subcategories/{subcategory_id}/) and the required Authorization: Bearer header — genuinely useful context. It stops short of describing failure modes (e.g., unknown ID) or the response payload.

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?

Three short labeled blocks, front-loaded with the purpose and then the endpoint and auth. Every line carries information; nothing is padded.

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 single-parameter read tool with no output schema, the definition covers purpose, endpoint, and authentication. The remaining gap — return value structure and error behavior — is minor given the tool's simplicity.

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% with a single parameter already documented as 'Subcategory ID (required)'. The description adds no format, source, or lookup information beyond the schema, so the baseline 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 gives a specific verb ('Retrieve') and resource ('a Subcategory by ID'), making the operation unambiguous. It does not explicitly differentiate itself from the sibling list_subcategories, but the 'by ID' framing implicitly separates the single-fetch case.

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?

There is no statement of when to use this tool versus alternatives such as list_subcategories, nor any prerequisites beyond the auth note. Usage must be inferred entirely from the parameter name.

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