list_relay_bounces

Retrieve bounced emails from relay sendings to identify permanent hardbounces and temporary softbounces. Filter by recipient, bounce type, date range, or correlation IDs to analyze delivery failures. Returns paginated data.

Instructions

List bounced mail relay emails. Hardbounces indicate permanent delivery failures; softbounces are temporary (e.g. mailbox full). Use this for relay-sent emails only; for event-triggered transactional bounces, use list_bounces instead. Filter by bounce type, recipient, relay sending ID, correlation IDs, or date range. Returns paginated HAL+JSON. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`bounceType`	No	Filter by bounce 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
`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, description carries full burden: discloses read-only safety status, explains domain semantics distinguishing hardbounces (permanent) from softbounces (temporary), and specifies return format (paginated HAL+JSON). Minor gap: no rate limit or auth details.

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 covering purpose, domain concepts, usage boundaries, filtering scope, return format, and safety. No redundancy with schema details; every sentence adds distinct value. Well front-loaded with the core action.

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 10 parameters with full schema coverage and no output schema, description adequately covers pagination behavior, bounce type semantics, and tool boundaries. Minor gap: doesn't describe specific response fields, though 'HAL+JSON' provides structural context.

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 has 100% description coverage, establishing baseline 3. Description categorizes filterable fields ('Filter by bounce type, recipient... date range') confirming capabilities without adding semantic depth (e.g., doesn't explain what correlation IDs represent or relay sending ID references).

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?

Description opens with specific verb and resource ('List bounced mail relay emails'), clearly distinguishing from sibling 'list_bounces' by specifying this is for 'relay-sent emails only' versus 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?

Explicitly states scope constraint ('Use this for relay-sent emails only') and names the correct alternative tool for other use cases ('for event-triggered transactional bounces, use list_bounces instead'), providing clear when-to-use guidance.

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