mark_notification_read

Purpose

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.

Required ability

account:write

Input schema

{
  "type": "object",
  "required": ["notification_id"],
  "properties": {
    "notification_id": { "type": "string", "description": "UUID of the entry to mark read, from list_notifications." }
  }
}

Output shape

{
  "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": {}
}

Example prompts

"I've dealt with the support backlog one — mark it read."

Failure modes

AUTHENTICATION_REQUIRED — no authenticated user on the request.
TOKEN_MISSING_ABILITY — token lacks account:write.
RESOURCE_NOT_FOUND — the id is not one of this creator's entries.