Skip to main content
Glama

List notifications

clipember_list_notifications
Read-onlyIdempotent

What the user's notifications bell shows, newest first (last 14 days, up to 30): posts that failed or couldn't be confirmed (with the reason in plain words, what to do and a help link), client comments, approvals and change requests on preview links, new teammates and team invites, and uploaded videos deleted automatically within 3 days. Read-only — it doesn't mark anything as read. To fix a failed post, see clipember_retry_failed_post.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses ordering (newest first), a retention window (last 14 days), a result cap (up to 30), and critically that it does not mark notifications as read — pre-empting the most likely side-effect assumption. It also notes auto-deleted videos appear within 3 days.

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 lead clause front-loads the resource and ordering, followed by a dense enumeration and a closing pointer to the retry tool. It is a single long sentence; the parenthetical detail on failed posts is useful but makes it slightly heavy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters and no output schema, the description carries the full burden of describing returned content and does so completely — item categories, ordering, window, cap, and the read-state behavior.

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?

The tool takes no parameters and schema coverage is trivially 100%, so there is nothing for the description to compensate for. Baseline 4 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 ('what the user's notifications bell shows') and then enumerates the exact item types returned, so an agent can distinguish it from siblings like clipember_list_post_comments or clipember_list_clips 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 Guidelines4/5

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

Implied usage is clear (surface user-facing notifications), and it explicitly routes the follow-up action: 'To fix a failed post, see clipember_retry_failed_post.' It does not state exclusions or when another list tool is preferable, keeping it short of a 5.

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