Skip to main content
Glama

Get Notification Counts

getNotificationCounts
Read-onlyIdempotent

Per-type notification counts for the authenticated user's current team. Narrow with unread, important, and with either severity (counts only that exact severity) or minSeverity (counts that urgency and above) — the two are mutually exclusive and a request carrying both is rejected with 400. Pass the same filters the feed is showing, so the counts describe the list the reader would land on. 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": "getNotificationCounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentsNoWhen 'mine', only count notifications for agents the authenticated user created (plus connection_broken, which is always counted), so the counts match a feed filtered the same way.
unreadNoIf true, only count unread notifications.
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 count notifications with exactly this severity, so the counts match a feed filtered the same way. Mutually exclusive with minSeverity.
importantNoIf true, only count notifications pinned to Important for you: unresolved, undismissed connection_broken rows you can reconnect yourself. Use it to size the sidebar alert without paging the list.
minSeverityNoOnly count notifications at or above this urgency, so the counts match a feed filtered the same way. 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
    • addedInput schema / properties / important
      Added value: +{
      +  "description": "If true, only count notifications pinned to Important for you: unresolved, undismissed connection_broken rows you can reconnect yourself. Use it to size the sidebar alert without paging the list.",
      +  "enum": [
      +    "true",
      +    "false"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context on top: a 400 rejection when both severity filters are sent, a 404 when the Notification Center feature is not enabled for the team, and the team-scoping rule tied to API key vs OAuth callers. These are failure modes an agent must anticipate and none are derivable from the annotations.

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?

Three sentences, front-loaded with the purpose before filters, constraints, and prerequisites. Dense with parenthetical clauses ('counts only that exact severity', 'counts that urgency and above') but each carries distinct filter semantics rather than filler.

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?

With no output schema, the description does communicate the return shape as per-type counts and ties it to a feed filtered the same way. Feature-availability and team-scoping behavior are covered; only the precise structure of the type keys in the response is left unspecified, which is a minor gap for a read-only counting tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning beyond the schema by foregrounding the severity/minSeverity mutual exclusion and its 400 consequence, plus the heuristic of mirroring the feed's filters. It does not add semantics for agents, automation_id, or team_id beyond what the already-detailed schema fields provide.

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 states a specific verb and resource: 'Per-type notification counts for the authenticated user's current team', which is concrete and scoped. It implicitly separates itself from the feed ('the counts describe the list the reader would land on') but never explicitly contrasts with the close sibling getUnreadNotificationCount, which returns a single total rather than per-type counts.

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 gives actionable usage guidance: narrow with unread/important/severity/minSeverity, and 'Pass the same filters the feed is showing' so the counts match the visible list. It clearly states severity and minSeverity are mutually exclusive, though it does not explicitly say when to prefer this tool over getUnreadNotificationCount for a simple badge count.

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