well_find_notion_mentions

io.github.WellApp-ai/well-mcp · Verify this server

Read every Notion page or comment that changed after `since` and names one of this workspace's own members — a person-valued property, an inline @mention in a page, or an @mention inside a comment. The match against a member comes only from Notion's own `<mention-user url="user://...">` tag: never a name, an email, or free text in the page's prose. This tool makes no judgment: it does not decide whether a page asks the member to act, is informational, is noise, or is an echo of a comment Well itself posted. That triage is the caller's own job, using each row's `zone`, `excerpt` and the fact that the row exists at all (a comment line Well itself wrote still carries no `<mention-user>` tag unless it names someone, so a plain acknowledgement never appears here). With no Notion connector live in this workspace, returns `connected: false` and reads nothing. Bounded at 25 changed pages per call, oldest changes first; `truncated: true` means either more pages changed than this call read, or a transient or connection failure (timeout, 5xx, rate limit, revoked grant) stopped the run partway through rather than skip the failed page. Either way, pass `cursor` as the next call's `since` and `cursor_note_id` as its `after_note_id` to keep going from the last page this call fully read, never re-reading what it covered and never skipping a page changed at the same instant. A failure that belongs to the connection (a revoked or expired grant, a missing scope or capability, a 401, 402 or 403, or any other typed 4xx outside the two codes below) stops the run at once with `truncated: true` and the cursor unchanged, so no page is lost while the member reconnects. A page whose own request is settled as wrong — Notion's own `object_not_found` code with a typed 404 or 410, or its `validation_error` code with a typed 400, and only those two — is skipped immediately, with no retry: its id and `updated_at` are reported in `failed_pages`, the cursor advances past it, and the run keeps reading later pages. A caller sees a page in `failed_pages` when mentions on that page may be incomplete for this and every future run, until the page is shared back or re-created. `dedup_key` is stable across runs for the same page/comment, zone and member: a caller uses it to never act on the same appearance twice.