Skip to main content
Glama

Mark Notification Batch Read

markNotificationBatchRead
Idempotent

Mark every unread live member of a notification batch as read for the authenticated user. Pass types to narrow the mark-read to those member types, and severity (exact) or minSeverity (threshold, mutually exclusive with severity) to narrow it by urgency — e.g. the page's active filters; omit them to mark every live member. Narrowing matters when the batch card was rendered under a filter: the rows marked read should be the rows the card counted. Pass openedFrom to record which channel the reader came through, on every member this call marks read. Pass automation_id to mark only the members about that automation, the ones its Notifications tab lists; a batch with none of them returns 404. Returns the count of members that were updated. Requires the Notification Center feature; returns 404 when it is not enabled for the team or the batch does not exist or belongs to another recipient/team.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "markNotificationBatchRead"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe notification batch's unique identifier
typesNo
team_idNoDuvo team UUID to operate on. API keys are pinned to a single team — omit this (it falls back to the key's team) or pass that same team; a different team is rejected. OAuth callers, who can span multiple teams, should pass the target team here.
severityNo
openedFromNo
minSeverityNo
automation_idNoOnly include notifications about this automation: notifications from runs in this automation (or, with no run, for its agents), notifications for its queues, connection_broken notifications for connections its agents use, and login_broken notifications for logins its agents sign in with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / automation_id
      Added value: +{
      +  "description": "Only include notifications about this automation: notifications from runs in this automation (or, with no run, for its agents), notifications for its queues, connection_broken notifications for connections its agents use, and login_broken notifications for logins its agents sign in with.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / types / items / enum
      Previous value: -[
      -  "connection_broken",
      -  "case_failed",
      -  "critical_case_issue",
      -  "case_issue",
      -  "critical_eval_issue",
      -  "eval_issue",
      -  "job_issue",
      -  "job_done",
      -  "background_job",
      -  "schedule_issue",
      -  "config_proposal"
      -]New value: +[
      +  "connection_broken",
      +  "login_broken",
      +  "case_failed",
      +  "critical_case_issue",
      +  "case_issue",
      +  "critical_eval_issue",
      +  "eval_issue",
      +  "job_issue",
      +  "job_done",
      +  "background_job",
      +  "schedule_issue",
      +  "config_proposal",
      +  "routine_candidate"
      +]
    • changedInput schema / properties / types / maxItems
      Previous value: -11New value: +13
  3. Changed1 schema field changed
    • addedInput schema / properties / openedFrom
      Added value: +{
      +  "enum": [
      +    "in_app",
      +    "email",
      +    "slack",
      +    "teams"
      +  ],
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • changedInput schema / properties / types / items / enum
      Previous value: -[
      -  "connection_broken",
      -  "case_failed",
      -  "critical_case_issue",
      -  "case_issue",
      -  "critical_eval_issue",
      -  "eval_issue",
      -  "job_issue",
      -  "job_done",
      -  "background_job",
      -  "schedule_issue"
      -]New value: +[
      +  "connection_broken",
      +  "case_failed",
      +  "critical_case_issue",
      +  "case_issue",
      +  "critical_eval_issue",
      +  "eval_issue",
      +  "job_issue",
      +  "job_done",
      +  "background_job",
      +  "schedule_issue",
      +  "config_proposal"
      +]
    • changedInput schema / properties / types / maxItems
      Previous value: -10New value: +11
  5. Changed2 schema fields changed
    • changedInput schema / properties / types / items / enum
      Previous value: -[
      -  "connection_broken",
      -  "critical_eval_issue",
      -  "eval_issue",
      -  "job_issue",
      -  "job_done",
      -  "background_job",
      -  "schedule_issue"
      -]New value: +[
      +  "connection_broken",
      +  "case_failed",
      +  "critical_case_issue",
      +  "case_issue",
      +  "critical_eval_issue",
      +  "eval_issue",
      +  "job_issue",
      +  "job_done",
      +  "background_job",
      +  "schedule_issue"
      +]
    • changedInput schema / properties / types / maxItems
      Previous value: -7New value: +10
  6. Changed2 schema fields changed
    • changedInput schema / properties / types / items / enum
      Previous value: -[
      -  "connection_broken",
      -  "job_issue",
      -  "eval_issue",
      -  "job_done",
      -  "background_job",
      -  "schedule_issue"
      -]New value: +[
      +  "connection_broken",
      +  "critical_eval_issue",
      +  "eval_issue",
      +  "job_issue",
      +  "job_done",
      +  "background_job",
      +  "schedule_issue"
      +]
    • changedInput schema / properties / types / maxItems
      Previous value: -6New value: +7
  7. First observed

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond the annotations: it discloses the return value (count of updated members), the Notification Center feature prerequisite, the 404 conditions (feature disabled, batch missing, or batch owned by another recipient/team), and the side effect that openedFrom is recorded on every member marked. Annotations cover idempotency and non-destructiveness, but the write's side effects are still spelled out, which is genuinely useful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Effectively front-loaded — the core action comes first, then narrowing rules, then optional parameters, then errors. It is dense but nearly every sentence carries information; the em-dash-heavy clauses make it a heavier read than necessary but nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter mutation with no output schema, the description covers the action, scoping filters, mutual exclusions, side effects, return value, feature gating, and 404 semantics. An agent has everything needed to call it correctly without opening the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 43%, the description carries most of the semantic load and does so well: types narrows member types, severity is exact vs minSeverity as threshold with mutual exclusion, openedFrom records the reader's channel, and automation_id enumerates which notifications qualify. The one gap is that the ordering of the severity enum is never defined, so an agent cannot tell where 'success' sits relative to 'warning' for a threshold parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with precise scope: 'Mark every unread live member of a notification batch as read for the authenticated user.' The 'batch'/'member' framing alone distinguishes it from single-notification mark-read siblings, and 'live' plus 'unread' define exactly which rows are in scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-and-when-not guidance: pass types/severity/minSeverity to narrow, omit them to mark every live member, and it explains why narrowing matters ('the rows marked read should be the rows the card counted'). It also states the mutual exclusivity of severity and minSeverity and the automation_id-only variant that can 404.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources