Skip to main content
Glama
Sign In
Eventbrite MCP Server

Eventbrite MCP Server

by mcpflow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_venue

Retrieve detailed information about an Eventbrite venue using its ID. Specify the venue ID to get name, address, and location details.

Instructions

Get information about a specific Eventbrite venue

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": {
      "venue_id": "<venue_id>"
    },
    "name": "get_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
venue_idYesEventbrite venue ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description's 'Get information' signals a read-only operation, but it does not disclose response format, error behavior, or authentication requirements. This is minimal but not misleading.

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?

A single clear sentence with no redundant words, perfectly front-loaded and efficient. Every word earns its place.

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 get-by-ID tool with one parameter and no output schema, the description covers the essential purpose. It could be enhanced by indicating common venue fields returned, but the current description is sufficient for selection and invocation.

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?

The schema provides 100% coverage for the sole parameter venue_id, and the description adds no additional syntax or format details beyond confirming it's a venue ID. The description's 'specific venue' aligns with the schema but offers no extra insight.

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 uses the specific verb 'Get' with the resource 'specific Eventbrite venue', clearly distinguishing it from sibling tools like search_events and get_categories. It also specifies the scope ('specific') implying retrieval by ID.

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?

The description implies usage when a specific venue ID is known, but it provides no explicit comparison to siblings or exclusions. It doesn't mention when to use search_events instead or any prerequisites.

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