Skip to main content
Glama

FlowCastle

by ai.flowcastle

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

TableJSON 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). 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.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's 'Read-only' is redundant, but it adds valuable beyond-annotation traits: 'Runs as SQL over the event tables, so it is safe on large workspaces' (performance/scalability), pagination behavior ('paginated, ordered by each contact's most recent matching event'), and the failure mode when goalKey is omitted ('fails with the list of known goal keys'). It does not disclose all potential error modes (e.g., missing blockId for BLOCK_SENT), but the goalKey discovery side effect is a strong behavioral detail.

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?

The description is a compact single paragraph of four sentences, each earning its place: definition, kind enumeration, behavioral traits, and a performance/alternative note. It is front-loaded with the purpose ('The reverse lookup') and uses parallel structure for the event kinds, making it easy to parse without wasted words.

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?

Given the complexity (13 parameters, 1 required, conditional requirements) and no output schema, the description covers the core invocation logic comprehensively, including all four event kinds and their parameter dependencies. However, it does not describe the return shape of the contacts (e.g., whether full contact objects or just IDs are returned), which is a gap given the absence of an output schema. Otherwise, it includes ordering, pagination, and the performance rationale, making it quite complete.

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 100%, so the baseline is 3. The description adds cross-parameter semantics by mapping each event kind to the required parameters (GOAL + goalKey, BUTTON_CLICK + blockId, etc.), which is not obvious from the flat schema. It also reveals the error/discovery behavior for missing goalKey (returns the list of known goal keys), adding meaning beyond the schema's individual parameter descriptions. This justifies a score above baseline.

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?

The description immediately identifies the tool as a 'reverse lookup' for contacts who triggered a specific analytics event, with explicit enumeration of the four event kinds (GOAL, BUTTON_CLICK, BLOCK_SENT, BROADCAST_DELIVERED) and their required parameters. It distinguishes itself from list_contacts by stating 'prefer it over paging list_contacts and checking each one', making the unique purpose unmistakable.

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?

The description provides clear when-to-use guidance: use this tool to find contacts matching an event, and explicitly prefers it over list_contacts for this scenario ('prefer it over paging list_contacts and checking each one'). It also gives conditional instructions per event kind (e.g., 'Omitting goalKey for kind GOAL fails with the list of known goal keys'), which helps the agent choose correct parameter combinations. The sibling list_contacts is named as the alternative, satisfying the explicit alternative condition.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Each get_/list_ tool targets a distinct resource and the descriptions carefully separate similar pairs like get_application_context vs get_workspace_summary and get_broadcast_details vs get_broadcast_analytics. The main ambiguity is apply_actions vs validate_actions, since one runs the other's validation, but the descriptions make that relationship explicit.

Naming Consistency4/5

Names consistently follow verb_object snake_case and use familiar verbs like create, get, list, and update. Minor deviations such as read_messages instead of list_messages, apply_actions/validate_actions with plural nouns, and run_flow_autotest are still predictable and readable.

Tool Count2/5

33 tools exceeds the 25-tool threshold and makes the surface feel heavy, even though the domain is broad. Many of the read-only getters are individually useful but could be consolidated, such as merging module catalog/details or workspace/application context.

Completeness4/5

Core workflows are covered: application lifecycle, flow editing through apply_actions, deployment, contacts, broadcasts, modules, and message/event reads. Minor gaps exist, such as no dedicated delete for contacts, applications, or broadcasts, and no rollback for deployments, but agents can work around or avoid these.

Resources