Inboxapp

Replay events

events_list

Read-onlyIdempotent

Replay events

Reads events in sequence order. A page can hold fewer than limit events when some are filtered out; continue from lastSeq while hasMore is true.

Input Schema

Name	Required	Description
`type`	No	Only these event types. Repeat the key to match any of several.
`limit`	No	Events to read, from 1 to 1000. Defaults to 100.
`afterSeq`	No	Exclusive. A webhook's `seq` resumes right after it. Omit to start at the oldest retained event.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / type / items / enum

Previous value: -[
-  "thread.created",
-  "thread.deleted",
-  "thread.assigned",
-  "thread.unassigned",
-  "thread.archived",
-  "thread.unarchived",
-  "thread.typing",
-  "message.sent",
-  "message.received",
-  "message.edited",
-  "message.deleted",
-  "message.reactionAdded",
-  "message.reactionRemoved",
-  "contact.statusChanged",
-  "contact.tagsChanged",
-  "contact.notesChanged",
-  "contact.valuationChanged",
-  "contact.assigneeChanged",
-  "tag.created",
-  "tag.updated",
-  "tag.deleted",
-  "status.created",
-  "status.updated",
-  "status.deleted",
-  "campaign.created",
-  "campaign.started",
-  "campaign.paused",
-  "campaign.resumed",
-  "campaign.completed",
-  "target.contacted",
-  "target.followUpSent",
-  "target.replied",
-  "connectionRequest.sent",
-  "connectionRequest.accepted",
-  "connectionRequest.withdrawn",
-  "follower.created"
-]New value: +[
+  "thread.created",
+  "thread.deleted",
+  "thread.assigned",
+  "thread.unassigned",
+  "thread.archived",
+  "thread.unarchived",
+  "thread.typing",
+  "message.sent",
+  "message.received",
+  "message.edited",
+  "message.deleted",
+  "message.reactionAdded",
+  "message.reactionRemoved",
+  "message.seen",
+  "contact.statusChanged",
+  "contact.tagsChanged",
+  "contact.notesChanged",
+  "contact.valuationChanged",
+  "contact.assigneeChanged",
+  "tag.created",
+  "tag.updated",
+  "tag.deleted",
+  "status.created",
+  "status.updated",
+  "status.deleted",
+  "campaign.created",
+  "campaign.started",
+  "campaign.paused",
+  "campaign.resumed",
+  "campaign.completed",
+  "target.contacted",
+  "target.followUpSent",
+  "target.replied",
+  "connectionRequest.sent",
+  "connectionRequest.accepted",
+  "connectionRequest.withdrawn",
+  "follower.created"
+]

Changed1 schema field changedOct 24, 2026
- addedInput schema / properties / afterSeq / maximum
```
Added value: +9007199254740991
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / type / items / enum

Previous value: -[
-  "thread.created",
-  "thread.deleted",
-  "thread.assigned",
-  "thread.unassigned",
-  "thread.archived",
-  "thread.unarchived",
-  "thread.typing",
-  "message.sent",
-  "message.received",
-  "message.edited",
-  "message.deleted",
-  "message.reactionAdded",
-  "message.reactionRemoved",
-  "contact.statusChanged",
-  "contact.tagsChanged",
-  "contact.notesChanged",
-  "contact.valuationChanged",
-  "contact.assigneeChanged",
-  "tag.created",
-  "tag.updated",
-  "tag.deleted",
-  "status.created",
-  "status.updated",
-  "status.deleted",
-  "campaign.created",
-  "campaign.started",
-  "campaign.paused",
-  "campaign.resumed",
-  "campaign.completed",
-  "target.contacted",
-  "target.followUpSent",
-  "target.replied",
-  "connectionRequest.sent",
-  "connectionRequest.accepted",
-  "connectionRequest.withdrawn"
-]New value: +[
+  "thread.created",
+  "thread.deleted",
+  "thread.assigned",
+  "thread.unassigned",
+  "thread.archived",
+  "thread.unarchived",
+  "thread.typing",
+  "message.sent",
+  "message.received",
+  "message.edited",
+  "message.deleted",
+  "message.reactionAdded",
+  "message.reactionRemoved",
+  "contact.statusChanged",
+  "contact.tagsChanged",
+  "contact.notesChanged",
+  "contact.valuationChanged",
+  "contact.assigneeChanged",
+  "tag.created",
+  "tag.updated",
+  "tag.deleted",
+  "status.created",
+  "status.updated",
+  "status.deleted",
+  "campaign.created",
+  "campaign.started",
+  "campaign.paused",
+  "campaign.resumed",
+  "campaign.completed",
+  "target.contacted",
+  "target.followUpSent",
+  "target.replied",
+  "connectionRequest.sent",
+  "connectionRequest.accepted",
+  "connectionRequest.withdrawn",
+  "follower.created"
+]

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / type / items / enum

Previous value: -[
-  "thread.created",
-  "thread.deleted",
-  "thread.assigned",
-  "thread.unassigned",
-  "thread.archived",
-  "thread.unarchived",
-  "thread.typing",
-  "message.sent",
-  "message.received",
-  "message.edited",
-  "message.deleted",
-  "message.reactionAdded",
-  "message.reactionRemoved",
-  "contact.statusChanged",
-  "contact.tagsChanged",
-  "contact.notesChanged",
-  "contact.valuationChanged",
-  "contact.assigneeChanged",
-  "tag.created",
-  "tag.updated",
-  "tag.deleted",
-  "status.created",
-  "status.updated",
-  "status.deleted",
-  "campaign.created",
-  "campaign.started",
-  "campaign.paused",
-  "campaign.resumed",
-  "campaign.completed",
-  "target.contacted",
-  "target.followUpSent",
-  "target.replied"
-]New value: +[
+  "thread.created",
+  "thread.deleted",
+  "thread.assigned",
+  "thread.unassigned",
+  "thread.archived",
+  "thread.unarchived",
+  "thread.typing",
+  "message.sent",
+  "message.received",
+  "message.edited",
+  "message.deleted",
+  "message.reactionAdded",
+  "message.reactionRemoved",
+  "contact.statusChanged",
+  "contact.tagsChanged",
+  "contact.notesChanged",
+  "contact.valuationChanged",
+  "contact.assigneeChanged",
+  "tag.created",
+  "tag.updated",
+  "tag.deleted",
+  "status.created",
+  "status.updated",
+  "status.deleted",
+  "campaign.created",
+  "campaign.started",
+  "campaign.paused",
+  "campaign.resumed",
+  "campaign.completed",
+  "target.contacted",
+  "target.followUpSent",
+  "target.replied",
+  "connectionRequest.sent",
+  "connectionRequest.accepted",
+  "connectionRequest.withdrawn"
+]

First observedOct 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-open-world, so safety is covered; the description adds real behavioral context: sequence ordering, short pages caused by filtering, and the hasMore/lastSeq continuation contract. Those response semantics appear nowhere else because there is no output schema, which makes this the only disclosure of the pagination loop.

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?

Two sentences, both informative, with the core behavior front-loaded. The leading 'Replay events' line merely restates the title and is dead weight, but everything after it earns its place.

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 3-optional-param read tool with no output schema, the description covers ordering, filtering side effects, and the full pagination loop, which is the critical missing piece. It stops short of describing what an event payload contains or the retention window hinted at by 'oldest retained event'.

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 type/limit/afterSeq are already well documented, and the description adds only the indirect note that filtering yields fewer than `limit` results. It does not clarify the interaction between `type` filtering and sequence ordering beyond that. Baseline 3 applies since the schema does the heavy lifting.

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 ('Reads events in sequence order'), which tells an agent this is a chronological event-log reader rather than a filtered entity lookup. However it never distinguishes itself from siblings like messages_history or threads_list, leaving the agent to infer why an event feed is preferable.

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

Usage Guidelines3/5

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

Provides concrete continuation guidance ('continue from `lastSeq` while `hasMore` is true') and implicitly points at filtering causing short pages. It gives no explicit when-to-use versus alternatives such as messages_history, and no prerequisites or scope constraints.

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

All Inboxapp tools Inspect

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

Need Help?