Preview email
preview_emailDisplay an email inline as a rendered document so users can visually inspect QR codes, barcodes, table layouts, tickets, boarding passes, invoices, or receipts; use get_email for content extraction.
Instructions
Show one email to the user as a rendered document, inline in the conversation. Use it when the user asks to see, show, or display an email or a document contained in one — tickets, boarding passes, invoices, receipts — where the visual rendering (QR codes, barcodes, table layouts) is the point. Use get_email instead when you need the content for reasoning, summarization, or extraction and the user does not need the pixels. The result gives the model only compact metadata; the rendered body is shown to the user by the client and is not in your context — do not claim to have read it from this call.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>"
},
"name": "preview_email"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The message id, as returned by search_emails or get_thread. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | ||
| from | Yes | ||
| tags | Yes | The message tags ($type/$label), e.g. "ticket" or "receipt". | |
| subject | Yes | ||
| renderSource | Yes | Whether the preview shows the HTML part or a plain-text fallback. | |
| attachmentCount | Yes |