Skip to main content
Glama

List notifications

list_notifications
Read-onlyIdempotent

What happened lately that the humans were told about (in the app and by email): posts that failed (fully or on some accounts, or only their first comment), accounts that need reconnecting, the X monthly limit reached, auto-reply rules failing repeatedly, accounts a client connected through a connect link, approvals given or changes requested, team members who joined, and posts waiting for the human to share them on a personal Facebook profile (post_handoff, with the share link). Newest first. Each item has a type, an English title and text, the facts in payload, and the app link. Useful to check on posts after scheduling them, or to tell the human what needs them.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly this kind
limitNoDefault 30
sinceNoOnly notifications after this time (ISO datetime)
workspace_idNoOnly this workspace (from list_workspaces)

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "post_failed",
      -  "account_reconnect",
      -  "x_limit",
      -  "rule_failing",
      -  "client_connected",
      -  "approval_decided",
      -  "member_joined"
      -]New value: +[
      +  "post_failed",
      +  "account_reconnect",
      +  "x_limit",
      +  "rule_failing",
      +  "client_connected",
      +  "approval_decided",
      +  "member_joined",
      +  "post_handoff"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/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 ordering ('Newest first') and mentions the post_handoff share link, which are genuine behavioral details. It does not discuss pagination or rate limits, but with a full output schema and safety annotations the remaining gaps are minor.

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

Conciseness3/5

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

The opening sentence is a long, parenthesis-heavy list that front-loads content but reads as a run-on. The information density is high and each clause maps to a notification type, but restructuring into shorter sentences would aid scanning.

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 annotations, full schema coverage, and an output schema, the description covers the remaining gaps: what events appear, ordering, and typical use. Nothing essential for correct invocation is missing.

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 coverage is 100% and all four parameters carry descriptions, so the schema does the heavy lifting. The description's enumeration of event kinds aligns with the `type` enum but adds no syntax or default detail beyond what the schema states.

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 clearly identifies the resource (notifications of human-facing events) and enumerates the eight event kinds matching the enum, so an agent knows exactly what comes back. The verb is implicit ('What happened lately...') rather than stated, but the resource and scope are unmistakable and no sibling tool covers the same ground.

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 concrete usage contexts: checking on posts after scheduling and telling the human what needs them. It does not name alternatives or state when not to use it, but for a single notifications endpoint the context is sufficient to route correctly.

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