Skip to main content
Glama

FlowCastle

by ai.flowcastle
OverviewDiscussionsAdmin

list_event_contacts

Read-only

The reverse lookup: which contacts triggered one analytics event — achieved a goal (kind GOAL + goalKey), clicked a button (BUTTON_CLICK + blockId, optionally buttonId/buttonIndex), were sent a block (BLOCK_SENT + blockId), or received a broadcast (BROADCAST_DELIVERED + broadcastId). Read-only, paginated, ordered by each contact's most recent matching event. Runs as SQL over the event tables, so it is safe on large workspaces — prefer it over paging list_contacts and checking each one. Omitting goalKey for kind GOAL fails with the list of known goal keys, which is the cheapest way to discover them.

Input Schema

NameRequiredDescriptionDefault
kindYesWhich event defines the audience: GOAL, BUTTON_CLICK, BLOCK_SENT, or BROADCAST_DELIVERED.
pageNo1-based page number. Defaults to 1.
botIdNoOnly contacts of this bot. Omit for all bots in the application.
limitNoContacts per page, between 1 and 100. Defaults to 20.
searchNoCase-insensitive substring matched against the contact name, username and platformId.
blockIdNoRequired for kind BLOCK_SENT and BUTTON_CLICK. Block id, from get_flow_context or get_block_details.
endDateNoOnly events at or before this time, same format as startDate. Defaults to now.
goalKeyNoRequired for kind GOAL. The goal key, e.g. "purchase".
buttonIdNoFor kind BUTTON_CLICK: narrow to one button. Format is `cb_{blockId}_{index}` over the block's buttons in editor order. Omit to count a click on any button of the block.
startDateNoOnly events at or after this time (ISO 8601 date string). Applies to every kind; for BROADCAST_DELIVERED the event time is when that contact's delivery was sent. Omit for the whole history — that is what "ever achieved this goal" needs.
broadcastIdNoRequired for kind BROADCAST_DELIVERED. Broadcast id, from list_broadcasts. Counts deliveries with status SENT, DELIVERED or READ.
buttonIndexNoFor kind BUTTON_CLICK: alternative to buttonId, the 0-based button position. Ignored when buttonId is set.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / startDate / description
      Previous value: -"Only events at or after this time (ISO 8601 date string). Omit for the whole history — that is what \"ever achieved this goal\" needs."New value: +"Only events at or after this time (ISO 8601 date string). Applies to every kind; for BROADCAST_DELIVERED the event time is when that contact's delivery was sent. Omit for the whole history — that is what \"ever achieved this goal\" needs."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/non-destructive, and the description adds real behavioral context on top: pagination, ordering by each contact's most recent matching event, SQL-over-event-tables execution, safety on large workspaces, and the exact failure mode when goalKey is missing. That is more than the safety profile the annotations provide.

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?

Front-loaded with the core identity, then the per-kind contract, then the routing advice. Every sentence carries new information — no restatement of the name or schema.

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 13-parameter tool with no output schema, the description covers conditional requirements, pagination, ordering, and failure behavior, which is nearly everything needed to call it correctly. It does not describe the shape of each returned contact, a minor gap given no output schema exists.

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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter semantics the schema states only per-field: which parameters are conditionally required per event kind and that omitting goalKey yields a helpful error listing valid keys. It stops short of explaining interaction details like startDate defaults for each kind.

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?

States a specific verb and resource ('which contacts triggered one analytics event') and enumerates the four event kinds with their required discriminators, so an agent knows exactly what this returns. It also explicitly distinguishes itself from list_contacts, naming it as the slower alternative.

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

Usage Guidelines5/5

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

Gives an explicit routing rule ('prefer it over paging list_contacts and checking each one') plus per-kind conditions (goalKey for GOAL, blockId for BLOCK_SENT/BUTTON_CLICK, broadcastId for BROADCAST_DELIVERED). It even documents a discovery workflow: omit goalKey to get the list of known keys.

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

All FlowCastle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources