trace_document
Read a receipt/invoice/forwarded email/Gmail receipt/PDF's lineage timeline: missing, skipped, income-routed, deduped or duplicate-removed documents. Not Gmail scan-job status/progress/completion (running/queued/finished/stuck): use get_scan_status; a scan is not a document.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "trace_document"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many days back to search. | |
| limit | No | Maximum lineage events to return. | |
| query | No | Merchant, sender, subject, invoice number, or phrase to search for, e.g. 'Blue Rocket', 'Driversnote', 'Uber receipt'. | |
| outcome | No | Optional processing outcome filter. | all |
| threadId | No | Gmail thread ID if known. | |
| messageId | No | Gmail message ID if known. | |
| receiptId | No | ExpenseBot receipt/invoice ID if known, e.g. IR-123, RO-abc, RR-456. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| type | Yes | ||
| message | Yes | ||
| success | Yes |