Skip to main content
Glama

Get Notification Feed

getNotificationFeed
Read-onlyIdempotent

List the notification feed for the authenticated user's current team, most recent activity first. Each item is either an individual notification or a notification batch (a per-agent group of job_issue/eval_issue/job_done/schedule_issue notifications). Filter with type, unread, and either severity (exact match) or minSeverity (threshold; the two are mutually exclusive); paginate with limit/cursor. Either severity filter also narrows a surfaced batch's counts to its qualifying members, and hides a batch with no qualifying live member. The feed is eventually consistent — a batch's counts can lag a concurrent write by one page fetch. 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": "getNotificationFeed"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly return individual notifications of this type and batches with at least one live member of it.
limitNo
agentsNoWhen 'mine', only return notifications for agents the authenticated user created. connection_broken notifications are always returned regardless, because they are not about an agent: a broken connection is only notified to the people who can act on it or escalate it, so filtering by agent authorship would hide it from the reader it was addressed to.
cursorNo
unreadNoIf true, only return unread individual notifications and batches with at least one unread live member.
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 individual notifications with exactly this severity, and batches with at least one live member of it. A batch's counts then describe only those members. Mutually exclusive with minSeverity. One of: info, warning, critical, success.
minSeverityNoOnly return individual notifications at or above this urgency, and batches with at least one live member at or above it. A batch's counts and worst severity then describe only its members at or above the threshold. 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. Changed1 schema field changed
    • 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. Changed1 schema field changed
    • 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. Changed1 schema field changed
    • 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. Changed1 schema field changed
    • 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. Changed1 schema field changed
    • changedInput schema / properties / agents / description
      Previous value: -"When 'mine', only return notifications for agents the authenticated user created. connection_broken notifications are always returned regardless, because a broken connection is everyone's to fix."New value: +"When 'mine', only return notifications for agents the authenticated user created. connection_broken notifications are always returned regardless, because they are not about an agent: a broken connection is only notified to the people who can act on it or escalate it, so filtering by agent authorship would hide it from the reader it was addressed to."
  7. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses eventual consistency for batch counts, that severity filters narrow a batch's counts and hide batches with no qualifying live member, and that a missing feature yields a 404. These are non-obvious behaviors an agent cannot get from the annotations or schema.

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?

The opening sentence front-loads scope and ordering, and subsequent sentences carry distinct information (batching, filters, consistency, prerequisite). It is dense but every clause adds behavior; the parenthetical type enumeration is the only slightly expendable part.

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 9-parameter, no-required-parameter list tool with no output schema, the description covers batching semantics, filter interactions, consistency, and the feature gate. The main remaining gap is the response envelope and cursor semantics, which are only alluded to via 'paginate with limit/cursor'.

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 78%, so the schema already explains most parameters, including the mine/agent-authorship exception and team_id pinning. The description restates the severity/minSeverity exact-match-versus-threshold distinction and mutual exclusivity, adding light consolidation but little meaning that is not already in the structured fields.

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

Purpose4/5

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

The description opens with a specific verb and resource ('List the notification feed for the authenticated user's current team, most recent activity first') and clarifies that each item is either an individual notification or a batch, which implicitly separates it from getNotification and getNotificationBatch. It stops short of naming those siblings explicitly, so routing still requires a small inference.

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

Usage Guidelines4/5

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

It states the supported filtering dimensions (type, unread, severity vs minSeverity with mutual exclusivity) and pagination via limit/cursor, plus the key prerequisite that the Notification Center feature must be enabled or a 404 is returned. It never says when to prefer getNotificationBatch or getUnreadNotificationCount instead of this feed.

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