mark_notification_read
Mark one entry of the creator's notification centre as read.
The bell's click for agents: one entry of the creator's notification centre is marked read, so the dashboard bell stops counting it. Idempotent: an entry already read keeps its first read_at. Take the id from list_notifications.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
Sending the same arguments twice changes nothing the second time.
Arguments
notification_id*stringUUID of the entry to mark read, from `list_notifications`.
What it returns
{ "data": { "id": "0b1f6e2a-7c3d-4e5f-8a9b-0c1d2e3f4a5b", "class": "support", "class_label": "Support", "title": "Support backlog in Signals", "body": "Three members are waiting for an answer.", "route": "projects.inbox", "params": { "projectId": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13" }, "url": "https://app.subscriby.net/projects/7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13/inbox", "read": true, "read_at": "2026-09-12T10:35:00Z", "created_at": "2026-09-12T10:05:30Z" }, "meta": {}}How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks account:write.
RESOURCE_NOT_FOUNDthe id is not one of this creator's entries.
How is this guide?
Last updated on
mark_all_notifications_read
Mark every unread entry of the creator's notification centre as read in one call.
Analytics & Reports Tools
Every figure the creator dashboard renders is readable here, from revenue and churn to the transaction list, computed by the same service layer, so an agent and the dashboard never disagree.