Find the thread, then read it

An inbox answer is a thread, not a summary. Narrow to the threads that can hold the answer, read the ones that do, and tie each claim to the message it came from.

1. Know which account you are reading

list_accounts first. Superhuman can link several accounts to one connection, and every other tool reads the primary one unless acting_email says otherwise. When the question could span accounts (a personal and a work inbox), run it once per account and say which one each result came from. An empty result from the wrong account looks exactly like a thread that does not exist.

2. Filter on people and time before words

list_threads takes from, to, subject_contains, body_contains, start_date, end_date, labels, and split. "The invoice from Stripe last month" is a sender and a date range, not a body search. Address filters match substrings, so a domain finds everyone at the company. body_contains is the widest net and ranks nothing, so pair it with a sender or a date range rather than running it alone.

Splits behave differently: split reads a precomputed membership list, so it ignores the date filters, and sort reorders only the page you got back. To walk a split by date, page with cursor and compare timestamps yourself.

3. Ask the question tool questions, not lookups

query_email_and_calendar answers a natural-language question across mail, calendar, and contacts ("what is still waiting on me from the Acme deal", "what is on my calendar Thursday"). Use it when the question spans threads or needs the calendar. Do not use it to fetch a thread you already identified: read that one with get_thread, because a synthesized answer blurs which message said what.

4. Read the thread before answering