Skip to main content
Glama

eventbrite_open

Open an Eventbrite page in your signed-in Cloud Browser to manage events, orders, attendees, sales reports, emails, refunds, and promo codes.

Instructions

Open a Eventbrite page in your signed-in Cloud Browser (default https://eventbrite.com) to work with events, orders, attendees, sales reports, emails, refunds and promo codes.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://eventbrite.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It usefully discloses that the page opens inside a 'signed-in Cloud Browser', signalling an authenticated, persistent session, but it says nothing about whether an existing tab is reused, whether navigation state is destroyed, or what the call returns to feed later tools.

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?

One front-loaded sentence with no wasted preamble; the trailing enumeration of supported business objects is slightly listy but does convey scope. A minor grammatical slip ('a Eventbrite') is the only blemish.

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 one-optional-parameter navigation tool with no annotations and no output schema, the definition covers the essentials. It leaves an agent guessing about what happens after opening — whether a handle or page content is returned and which sibling tool to chain next.

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 coverage is 100% and the single optional url parameter is already documented with its default. The description only restates the default URL, adding no format, path, or validation detail beyond the schema.

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?

States a specific verb ('Open') and resource ('Eventbrite page in your signed-in Cloud Browser'), which is clearly distinct from click/type/read/close siblings. It stops short of naming those siblings or saying this is the entry point that must precede them.

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 phrase 'to work with events, orders, attendees, sales reports, emails, refunds and promo codes' implies when this tool applies, and the signed-in-browser mention implies an auth prerequisite. There is no explicit when-not guidance or referral to alternatives for reading or interacting with a page.

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