list_relay_reactions

List recipient reactions (opens and clicks) for SMTP relay emails to track engagement. Filter by date range, recipient, reaction type, or sending ID for detailed delivery analytics.

Instructions

List recipient reactions (opens and clicks) for mail relay emails sent via SMTP relay. Use this to track engagement on relay-sent emails. For reactions on event-triggered transactional emails, use list_reactions instead. Filter by reaction type, recipient, relay sending ID, correlation IDs, or date range. Returns paginated HAL+JSON. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`reactionType`	No	Filter by reaction type
`email`	No	Filter by recipient email
`relaySendingId`	No	Filter by relay sending ID
`correlationId1`	No	Custom correlation ID 1
`correlationId2`	No	Custom correlation ID 2
`correlationId3`	No	Custom correlation ID 3
`trackingHash`	No	Filter by tracking hash
`begin`	No	ISO 8601 start date
`end`	No	ISO 8601 end date
`size`	No	Page size (max 500, default 200)
`page`	No	Page number (default 0)

Tool Definition Quality

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and successfully discloses: read-only nature ('Read-only'), return format ('Returns paginated HAL+JSON'), and scope limitations. It could improve by mentioning default sorting or time range limits if any exist.

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?

Six sentences, zero waste. Front-loaded with purpose (List recipient reactions...), followed by usage context, sibling differentiation, parameter summary, and technical metadata. Every sentence 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?

Given 11 parameters (all optional), no output schema, and no annotations, the description adequately covers the tool's purpose, filtering capabilities, output format, and safety profile. Minor gap: doesn't mention that all parameters are optional or explain correlation ID purpose.

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%, establishing a baseline of 3. The description summarizes available filters ('Filter by reaction type, recipient...') but adds no semantic depth beyond the schema's own descriptions (e.g., doesn't explain what correlation IDs represent or how to obtain a relaySendingId).

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 explicitly states the action ('List recipient reactions'), the specific resource ('mail relay emails sent via SMTP relay'), and the reaction types ('opens and clicks'). It clearly distinguishes from the sibling tool 'list_reactions' by specifying this is for 'relay-sent emails' vs 'event-triggered transactional emails'.

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?

Provides explicit when-to-use guidance ('Use this to track engagement on relay-sent emails') and explicitly names the alternative tool for different contexts ('For reactions on event-triggered transactional emails, use list_reactions instead').

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

Install Server

Inxmail MCP