Skip to main content
Glama

Build List From Events

build_list_from_events

Build ONE deduplicated list of everyone who RSVPed to / held a ticket for several of your events (e.g. every past dinner in a series) — give event_ids (from list_events) and a list_name (found or created). Same person across events counts once (by account, else email). Returns people, per-event counts, how many have an email, and how many you may email marketing (recorded permission or community email opt-in). Optional where: min_tickets (bought, e.g. 2 = "2 or more"), min_events_attended, checked_in_only, min_net_spend_cents + currency (USD default) — only people meeting every condition are kept; the result states the rule and counts (matched). Optional list_id pins a stable id for a new list so a campaign draft in the same plan can target it. dry_run counts without writing. Never records consent. Requires a connected account; you must host every event.

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": {
      "event_ids": "<event_ids>",
      "list_name": "<list_name>"
    },
    "name": "build_list_from_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
whereNo
dry_runNo
list_idNo
event_idsYes
list_nameYes
community_idNo
include_cancelledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / community_id
      Added value: +{
      +  "pattern": "^[\\w-]{1,128}$",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / list_id
      Added value: +{
      +  "pattern": "^[A-Za-z0-9_-]{8,64}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / where
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "checked_in_only": {
      +      "type": "boolean"
      +    },
      +    "currency": {
      +      "pattern": "^[A-Za-z]{3}$",
      +      "type": "string"
      +    },
      +    "min_events_attended": {
      +      "maximum": 50,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "min_net_spend_cents": {
      +      "maximum": 9007199254740991,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "min_tickets": {
      +      "maximum": 1000,
      +      "minimum": 1,
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare a write (readOnlyHint=false) that is non-destructive and non-idempotent, and the description adds real value beyond them: dedupe key precedence, that list_name may be found or created, that dry_run counts without writing, and that it never records consent. Missing: what happens when an existing list_name collides, whether members are appended or replaced, and rate/size limits beyond the 50-event cap in the schema.

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?

Purpose is front-loaded in the first clause, then return shape, then optional filters, then the dry_run/list_id escape hatches, then constraints. Dense and long, but every clause carries a fact an agent would otherwise have to guess.

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 7-parameter, nested-schema, no-output-schema tool this is close to sufficient: it describes returns inline, constraints on hosting, and the filter AND-semantics. Two parameters (community_id, include_cancelled) and the collision behavior for an existing list_name remain undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load and largely does: it explains event_ids provenance (from list_events), list_name found-or-created, every 'where' sub-filter including what min_tickets means and currency defaulting to USD, list_id's purpose, and dry_run. community_id and include_cancelled are left unexplained.

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 and resource: build one deduplicated list of RSVPs/ticket-holders across several events, deduped per person by account then email. The mechanism distinguishes it well from list-building siblings such as save_people_as_list, but no sibling is named explicitly and no alternative routing is offered.

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?

Gives a clear triggering context ('several of your events (e.g. every past dinner in a series)') and prerequisites ('Requires a connected account; you must host every event'), plus when to choose dry_run. It does not say when NOT to use it or which sibling to prefer for adjacent jobs (importing contacts, saving an existing people set).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.