Skip to main content
Glama

eventbrite_click

Clicks a numbered element on the current Eventbrite page so AI agents can act on listings, orders, or attendee details identified from the last page read.

Instructions

Click a numbered element on the current Eventbrite page.

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": {
      "element": "<element>"
    },
    "name": "eventbrite_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether the click navigates to a new page, whether it mutates server state, what happens if the element number is stale or invalid, or whether the page context changes afterward — all critical for an actuating tool.

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?

A single compact sentence with the target front-loaded and no filler. Its brevity is efficient, though it borders on under-specification for an action tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and a mutation-style action that drives a browser, the definition leaves out what an agent most needs: post-click behavior, error conditions, and page-state effects. Adequate naming is not enough for this complexity.

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 schema already states 'Element number from the last read,' so the description's mention of numbered elements largely repeats structured data rather than adding new meaning such as numbering scheme or staleness rules. Baseline 3 is appropriate.

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 ('Click') and a specific target ('a numbered element on the current Eventbrite page'), which is clearly distinct from siblings like eventbrite_type or eventbrite_read. It stops short of naming or contrasting those siblings, but the purpose is unambiguous.

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 'element number from the last read' implies the prerequisite of calling eventbrite_read first and implies usage on the active page, but there is no explicit when-to-use vs. when-to-prefer-type/open/close guidance or statement of exclusions.

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