Skip to main content
Glama
PhononX

Carbon Voice

by PhononX

list_inbox_notifications

Read-only

Retrieve inbox notifications with total unread count. Filter by category, such as mentions, to see what you missed or where you were mentioned.

Instructions

List your inbox notifications, with a total unread count. USE WHEN: Answering "what did I miss" or "where was I mentioned" — pass category: "mentions" for mentions. The response includes total_unread, so you can report a count without paging. USE INSTEAD: search_message_ids with notified_status if you want the messages themselves rather than notification records. search_messages_by_heard_status for unlistened messages. EXAMPLE: {"category":"mentions","limit":25} RETURNS: {results: [...], total_results, total_unread, filters}. Pages with skip/limit, not cursors. NARROW: pass response_fields ["results","total_unread","total_results"] unless you need more — the full payload is much larger.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoAnchor as a UNIX timestamp in MILLISECONDS (e.g. 1694313500106) — not an ISO string.
skipNoOffset for paging. This endpoint uses skip/limit, not cursors.
typeNoNarrow to a single notification type (e.g. `channel.users.added`). Prefer `category` unless you know the exact type string.
limitNoNumber of notifications to return (max 100).
categoryNoNotification category. `mentions` is the one to use for "where was I mentioned".
directionNoDirection to walk from the anchor.newer
response_fieldsNoDot-path allowlist to shrink the response, e.g. ["results.id","total"]. Omit for the full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.10.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses pagination behavior (skip/limit, not cursors), the presence of total_unread, the response shape, and the large payload cost with a NARROW recommendation. This adds meaningful operational context that annotations alone do not provide.

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?

The description is well-structured with labeled sections (USE WHEN, USE INSTEAD, EXAMPLE, RETURNS, NARROW), front-loads the core purpose, and every section earns its place. It packs substantial routing and response information into a compact, scannable format.

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?

Despite having no output schema, the description explains the return structure, unread count, pagination model, and payload optimization. Combined with a fully described input schema, it gives an agent everything needed to select and invoke this tool correctly.

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 already 100%, so the baseline is 3. The description adds value by telling agents to pass category: 'mentions' for mention queriesтся and to pass response_fields ['results','total_unread','total_results'] to shrink the payload, which is practical guidance beyond schema definitions.

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?

The description opens with a specific verb and resource: 'List your inbox notifications, with a total unread count.' It clearly distinguishes itself from message-search siblings by emphasizing notification records rather than messages, so an agent can tell it apart from search_message_ids and search_messages_by_heard_status.

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?

'USE WHEN' explicitly maps common user intents like 'what did I miss' to this tool, including the category parameter for mentions. 'USE INSTEAD' names the exact alternative tools and the conditions under which they should be preferred, giving agents clear routing guidance.

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