Sequencer Event Poller MCP Server

Poll sequencer events

poll_sequencer_events

Read-only

Read replies, bounces, unsubscribes, meetings, and LinkedIn replies across Instantly, Smartlead, HeyReach, and lemlist for a chosen time window, returning one flat row per event and a run summary. Read-only.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "poll_sequencer_events"
  }
}

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, up to 50000. Each event row is billed. 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, 1 to 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, 1 to 100. 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.

Changed14 schema fields changedOct 29, 2026

changedInput schema / properties / max_events / description

Previous value: -"Event rows per run, oldest first. Default 5000."New value: +"Event rows per run, oldest first, up to 50000. Each event row is billed. Default 5000."

removedInput schema / properties / max_events / maximum
```
Removed value: -50000
```
removedInput schema / properties / max_events / minimum
```
Removed value: -1
```
changedInput schema / properties / max_events / type
```
Previous value: -"integer"New value: +"string"
```

changedInput schema / properties / max_pages_per_query / description

Previous value: -"Pages of 100 records per vendor query. Default 20."New value: +"Pages of 100 records per vendor query, 1 to 100. Default 20."

removedInput schema / properties / max_pages_per_query / maximum
```
Removed value: -100
```
removedInput schema / properties / max_pages_per_query / minimum
```
Removed value: -1
```
changedInput schema / properties / max_pages_per_query / type
```
Previous value: -"integer"New value: +"string"
```
addedInput schema / properties / only_new / enum
```
Added value: +[
+  "true",
+  "false"
+]
```

changedInput schema / properties / only_new / type

Previous value: -"boolean"New value: +"string"

changedInput schema / properties / since_hours / description

Previous value: -"Read events from this many hours before the run, at most 2160 (90 days). Default 24. Ignored when since is set."New value: +"Read events from this many hours before the run, 1 to 2160 (90 days). Default 24. Ignored when since is set."

removedInput schema / properties / since_hours / maximum
```
Removed value: -2160
```
removedInput schema / properties / since_hours / minimum
```
Removed value: -1
```
changedInput schema / properties / since_hours / type
```
Previous value: -"integer"New value: +"string"
```

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?

Goes well past the readOnlyHint annotation: names the env-var keys, states that keyless vendors are skipped, discloses APIFY_TOKEN requirement, per-event-row billing, and that failed runs return an error with a run ID. These are exactly the operational facts an agent needs before spending money.

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?

One dense but well-ordered paragraph: what it reads, what it returns, how auth resolves, safety, billing. No filler sentences, though the single block makes the billing/requirement notes easy to miss.

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?

With 13 optional parameters and no output schema, the description still specifies the row shape, the summary row, defaults for skipping and vendor selection, and cost implications. Nothing an agent needs to call it safely is absent.

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 each parameter already carries a clear description, so baseline is 3. The prose adds return-shape detail (flat rows, free summary row) and the billing implication of max_events, but no syntax or format guidance beyond the schema.

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 (read/poll) and resource (sequencer events) plus the exact event categories and the four vendor sources. An agent knows precisely what comes back and from where without opening the schema.

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?

Frames the tool as a time-window poll across the caller's own accounts and mentions the only_new default that skips already-returned events, which is real usage context. There are no sibling tools to differentiate against and no explicit when-not-to-use guidance, so it stops 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