Skip to main content
Glama

list_notifications

Read-onlyIdempotent

The workspace's in-app notifications, newest first: a post published, a post that failed or is running late, a plan slot for today with nothing scheduled, a follower or views milestone.

limit is 1–50; unread_only=true returns just the ones not yet read in the app. This reads only — it does not mark anything read. Use it to answer "did that reel go out?" or "anything fail overnight?" (a failed post's reason is in list_scheduled_posts' publish_error).

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
unread_onlyNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
itemsYes
unread_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by clarifying that listing does NOT mark notifications read (a plausible but wrong assumption) and that results are ordered newest first. It does not cover pagination or what happens beyond the limit cap.

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?

Two short blocks: the first front-loads what is listed and the result ordering, the second covers parameter behavior, the read-only guarantee, and the sibling hand-off. The event-type enumeration earns its space by defining scope; nothing is 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?

An output schema exists and annotations cover the safety profile, so the description needs only scope, ordering, and parameter meaning — all present. Minor gaps are the unstated default limit and no mention of what happens past 50 notifications.

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 0% schema description coverage, the description carries the load: it explains the 1–50 range for limit and the meaning of unread_only=true ('just the ones not yet read in the app'). workspace_id is only implied by 'The workspace's,' and the default limit of 20 is not stated, so it stops short of full compensation.

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 ('The workspace's in-app notifications, newest first') and enumerates the concrete event types it surfaces (published post, failed/late post, empty plan slot, follower/views milestone). This lets an agent tell it apart from siblings like list_scheduled_posts without opening a schema.

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 concrete trigger questions ('did that reel go out?', 'anything fail overnight?') and explicitly routes the failure-detail case to list_scheduled_posts' publish_error, so the agent knows both when to call this and where to go for detail it doesn't provide.

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