Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List notifications

list_notifications
Read-onlyIdempotent

Your Skool notifications: new posts, comments, mentions, likes and approvals, newest first. Lists the bell's notifications for this account, newest first, from all groups or one: what happened (type, such as new-post, comment, mention, like), the line Skool shows, the post it is about and a link. unread_only keeps the unread ones. Reading them does not mark them read; mark_notifications_read does.

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
groupNoOnly this group's notifications, by URL name. Default: all groups.
limitNo1 to 30. Default: 30.
cursorNoNext page cursor from the previous call.
unread_onlyNoOnly unread ones. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false. The description adds real value beyond them: that reading does NOT mark items read, that results are newest-first, and what each item contains (type, line, post, link). Pagination depth is left to the 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?

Front-loaded with the core action and scope, and each sentence carries information. Slight redundancy in stating 'newest first' twice and a somewhat run-on second sentence keep it from a 5.

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 helpfully enumerates the returned fields (type, line, post, link) and notes the newest-first ordering and non-mutating read behavior. Enough for an agent to call it correctly; cursor pagination is only implied.

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%, with each of the four parameters described inline including defaults and the 1–30 limit range. The description only reinforces 'group' scoping and 'unread_only', adding little beyond the schema, so the baseline 3 applies.

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 ('Lists ... notifications') plus the content scope (new posts, comments, mentions, likes, approvals) and ordering (newest first). It also distinguishes itself from mark_notifications_read by naming that sibling explicitly.

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?

Gives clear selection criteria: all groups vs one via 'group', and 'unread_only keeps the unread ones'. It routes the agent to mark_notifications_read for the adjacent task. No explicit "when not to use" beyond that, so 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Skool MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources