Client area

MCP tool · Email

trace_email

Trace what happened to a customer's mail in the mail-server log: per message the delivery verdict (delivered / bounced / deferred / frozen / queued) with the remote…

trace_email
R Read
Scope read:email
Read-onlyIdempotentOpen-world

Description

Trace what happened to a customer's mail in the mail-server log: per message the delivery verdict (delivered / bounced / deferred / frozen / queued) with the remote host, the SMTP error or defer reason, sender, recipient, subject and timestamps. Accepts an email, a domain, or a service id. It reads the log over SSH on the hosting node, so it may degrade to an empty result with a note; that is not an error, just no data available.

Input

Name Type Description
input required string An email address (matched as sender or recipient), a domain (any address on it), or an Inleed service id. Resolved to the owning account; the resolved target is echoed back.
days integer How many days of the mail log to search. Defaults to 2; larger values read rotated logs and cost more. Range 1–30.
limit integer Maximum messages to return, newest first. Defaults to 25 to protect the response budget. Range 1–200.

Example conversation

User

Did my email reach [email protected]?

Assistant

Three attempts yesterday: two delivered, one bounced (recipient mailbox full).

Illustrative. The assistant calls trace_email behind the reply; tier R decides whether it executes directly or returns a confirmation link.

Esc
navigate open Esc close