Skip to main content
Glama

List Notifications

listNotifications
Read-onlyIdempotent

List notifications for the authenticated user's current team, most recent first. Filter with type, unread, severity or minSeverity (mutually exclusive), important, agentRunId, or processId; paginate with limit/cursor. Pass batchId to list only the live members of a notification batch, optionally ordered by sort=importance (only valid together with batchId). Requires the Notification Center feature; returns 404 when it is not enabled for the team.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
sortNoimportance orders by type importance then severity (only valid together with batchId); default recency.recency
typeNoOnly return notifications of this type. One of: 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.
limitNoNumber of notifications per page (1-100, default 30).
cursorNoOpaque cursor from the previous page's nextCursor. Omit for the first page.
unreadNoIf true, only return unread notifications.
batchIdNoOnly return live members of this notification batch.
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.
severityNoOnly return notifications with this severity. One of: info, warning, critical, success.
importantNoIf true, only return important notifications: unresolved connection_broken rows pinned until reconnected, removed, or dismissed.
processIdNoOnly return notifications about this Clarity process.
agentRunIdNoOnly return notifications about this agent run.
minSeverityNoOnly return notifications at or above this urgency. Least to most urgent: success < info < warning < critical. Mutually exclusive with severity.
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 / type / description
      Previous value: -"Only return notifications of this type. One of: 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: +"Only return notifications of this type. One of: 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 / type / 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"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Only return notifications of this type. One of: connection_broken, case_failed, critical_case_issue, case_issue, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue."New value: +"Only return notifications of this type. One of: 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 / type / 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"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Only return notifications of this type. One of: connection_broken, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue."New value: +"Only return notifications of this type. One of: 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 / type / 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"
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Only return notifications of this type. One of: connection_broken, job_issue, eval_issue, job_done, background_job, schedule_issue."New value: +"Only return notifications of this type. One of: connection_broken, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue."
    • changedInput schema / properties / type / 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"
      +]
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations: default recency ordering, the batch-only constraint for sort=importance, and the 404 behavior when Notification Center is not enabled. It stops short of describing response shape or additional auth details.

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

Conciseness5/5

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

Three sentences, front-loaded with the core purpose, then filter/pagination guidance, then batch and feature-gate constraints. The wording is dense and efficient, with no boilerplate or unnecessary repetition.

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

Completeness4/5

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

For a 13-parameter read-only list tool, the description covers feature availability, ordering, filtering, pagination, and batch semantics. It does not describe the returned notification shape or pagination response fields, which is a minor gap given there is no output schema, but the cursor parameter schema partially compensates.

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

Parameters3/5

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

Schema description coverage is 100%, so all 13 parameters are already documented in the schema. The description groups the filters and restates mutual exclusivity and the batchId/sort dependency, but adds little new parameter meaning beyond the schema itself, making the baseline score appropriate.

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: "List notifications" for the authenticated user's current team, most recent first. The batchId variant is also explicitly scoped, so an agent can distinguish normal notification listing from batch-member listing.

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

Usage Guidelines3/5

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

Explains how to filter and paginate, when batchId/sort apply, and that the Notification Center feature is required. However, it does not explicitly compare this tool with sibling alternatives such as marking or deleting notifications, so usage is mostly implied by the tool's purpose.

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