Sequencer Event Poller MCP Server

Poll sequencer events

poll_sequencer_events

Read-only

Reads replies, bounces, unsubscribes, meetings, interest changes, and LinkedIn replies across your Instantly, Smartlead, HeyReach, and lemlist accounts for a time window, returning one flat row per event.

Instructions

Read replies, bounces, unsubscribes, meetings booked, interest changes, and LinkedIn replies from your own Instantly, Smartlead, HeyReach, and lemlist accounts for a time window. Returns one flat row per event (vendor, event type, time, lead email and name, company, campaign, reply text where the vendor returns it) plus one free run summary row with counts and the status of each vendor. Vendor keys are read from this server's environment (INSTANTLY_API_KEY, SMARTLEAD_API_KEY, HEYREACH_API_KEY, LEMLIST_API_KEY); vendors with no key are skipped. Read-only: it never creates, edits, pauses, or sends anything in a sequencer. A run that does not succeed is returned as an error with its run ID. Requires an APIFY_TOKEN and is billed per event row.

Input Schema

Name	Required	Description
`since`	No	Optional start of the window in UTC, for example 2026-10-20T00:00:00Z.
`until`	No	Optional end of the window in UTC. Default now.
`only_new`	No	Skip events an earlier run already returned (free). Default true.
`state_key`	No	Optional name for the only new events memory, so two schedules keep separate memories.
`max_events`	No	Event rows per run, oldest first. Default 5000.
`event_types`	No	Which events to return. Default: reply, linkedin_reply, bounce, unsubscribe, meeting_booked, interested, connection_accepted.
`since_hours`	No	Read events from this many hours before the run, at most 2160 (90 days). Default 24. Ignored when since is set.
`max_charge_usd`	No	Optional. The run stops before a charge that would pass this amount.
`max_pages_per_query`	No	Pages of 100 records per vendor query. Default 20.
`lemlist_campaign_ids`	No	Read only these lemlist campaigns (cam_ ids). Empty: all campaigns.
`heyreach_campaign_ids`	No	Read only these HeyReach campaigns (numeric ids). Empty: all campaigns.
`instantly_campaign_ids`	No	Read only these Instantly campaigns (UUIDs). Empty: all campaigns.
`smartlead_campaign_ids`	No	Read only these Smartlead campaigns. Empty: all non draft campaigns.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint/destructiveHint/openWorldHint), the description discloses the auth model (env var API keys, APIFY_TOKEN required), skip behavior for missing keys, per-row billing, dedupe memory semantics via only_new, and that failed runs return an error carrying a run ID. That is substantive operational context an agent cannot get from the annotation block.

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?

Front-loaded with the core action and output shape, then cost/auth/error caveats. The read-only sentence partly restates readOnlyHint/destructiveHint, but it is specific enough about what is never touched (create, edit, pause, send) to justify its length. No filler sentences.

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

Completeness5/5

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

For a 13-parameter, no-output-schema tool, the description covers return contents (flat event rows with named fields plus a summary row with counts and per-vendor status), error behavior, auth requirements, and cost. Combined with full schema coverage, an agent has everything needed to call it correctly.

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 description coverage is 100%, so every one of the 13 parameters is already documented with defaults, bounds, and formats. The description adds only the time-window framing and env-key note; it does not explain parameter interactions (e.g. since vs since_hours vs only_new) beyond what the schema states, so the baseline 3 applies.

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 names a specific verb (read/poll), the exact resource (sequencer events), enumerates the event kinds and the four vendors covered, and states the output shape. There are no sibling tools, so no differentiation is needed, and the scope 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 Guidelines4/5

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

It establishes the operating context clearly: events from your own accounts, within a time window, with unconfigured vendors silently skipped and billing per event row. With no sibling tools there are no alternatives to route against, but it never states an explicit 'do not use when' condition, which keeps it short of a 5.

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

Deploy Server

Other Tools

poll_sequencer_eventsA