Skip to main content
Glama

eventbrite_guide

Guides you through Eventbrite tasks such as managing events, orders, attendees, refunds, and promo codes, including screen navigation and the sign-in link. Call this first.

Instructions

How to work in Eventbrite (events, orders, attendees, sales reports, emails, refunds and promo codes): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "eventbrite_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Eventbrite, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. Calling it a 'guide' and saying 'call this first' implies a non-mutating prerequisite, and the mention of a sign-in link hints at authentication context, but it never states that the tool performs no browser actions, has no side effects, or what it returns.

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?

Two sentences, with the purpose stated first and the imperative 'Call this first' front-loaded at the end for emphasis. The parenthetical topic list is long but each item signals a supported domain, so little is wasted.

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?

For a simple one-parameter orientation tool with no output schema, the description covers what topics the guide addresses. It leaves open whether the guide returns instructions or performs actions itself, and how the returned guidance relates to the sibling browser-control tools.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains 'task' as the user's goal in their own words. The description adds no format hints, examples, or scoping advice for that parameter, 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 names a specific resource — a guide covering Eventbrite screens, the sign-in link, and domains like events, orders, attendees, and refunds. That is well beyond a tautology, though it never states the output form (prose instructions vs. a URL) and does not explicitly contrast itself with the eventbrite_click/open/type action tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' is an explicit ordering directive that tells an agent when this tool precedes the sibling action tools. There is no when-not guidance or statement about whether it should be re-called per task versus once per session, which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.