follow_ups
Identifies Gmail threads you're waiting on or that await your reply, so you can decide whom to nudge and whom to answer.
Instructions
Who is waiting on whom. waitingOnThem: threads whose LAST message is yours (SENT) and has had no answer for at least nudgeAfterDays — candidates for a nudge; a note to yourself (every To and Cc address is the account's own primary address, in any spelling Gmail delivers to it: +tags, dots, googlemail.com) is left out; one other recipient keeps it. waitingOnMe: threads still in the inbox whose last message came from someone else — a person, not a newsletter or an automated notice by its own headers — oldest first. Decided on each thread's last message and its LIVE labels: the search index only proposes candidates (in:sent / in:inbox within the last days), so a thread the index still files under the inbox after it was archived is dropped, as in search. Drafts, trash and spam messages do not count as a thread's last word. Scans at most max threads per side; hasMore says when more candidates existed. A thread with no recorded date is left out rather than given an invented age. USE WHEN: 'what am I waiting on?', 'who have I not answered?', 'what should I follow up on?' DO NOT USE: as an inbox overview (use triage_digest) or to read a thread (use get_thread). SIDE EFFECTS: none.
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": "follow_ups"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| max | No | ||
| days | No | ||
| nudgeAfterDays | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hasMore | Yes | ||
| scanned | Yes | ||
| waitingOnMe | Yes | ||
| waitingOnThem | Yes |