Skip to main content
Glama
Sign In

Hailbell

by com.hailbell.api
OverviewDiscussionsAdmin

list_notifications

Read-only

The latest notifications, newest first, with their numbers. With appId only: that platform's notifications, including its part of campaigns across platforms (groupId). With productId or platforms: the app's campaigns, each campaign across platforms once with its numbers per platform.

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
appIdNoThe app to act on, from list_apps. Optional when the key belongs to one app.
limitNo
platformsNoSeveral platforms of one app in one campaign: "all", or a list of "ios", "android", "web" (or App IDs). Each person gets it once. Omit (with no productId) for the one platform of appId.
productIdNoThe whole app (productId from list_apps), for a campaign across its platforms. Same as appId of any platform with platforms "all".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly and closed-world annotations, the description discloses newest-first ordering, campaign grouping across platforms, and deduplication ('each campaign across platforms once'). It still omits pagination or response-shape details, but it adds meaningful behavioral context.

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 first sentence is concise and front-loaded, but the second is dense and awkwardly phrased, especially 'including its part of campaigns across platforms (groupId)' and the repeated 'numbers' concept. It avoids obvious filler but trades clarity for compression.

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

Completeness3/5

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

This is a four-parameter, mode-dependent list tool with no output schema, so the description should carry more of the return and pagination burden. It explains grouping behavior but leaves the limit semantics, pagination behavior, and what 'numbers' actually are undefined.

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 75%, and the description adds real meaning for appId, productId, and platforms by explaining how they select platform notifications versus whole-app campaigns. The limit parameter remains undocumented in both schema and description, so it is not complete.

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 identifies the resource and ordering: 'The latest notifications, newest first.' It also explains the two main scoping modes, though 'with their numbers' is vague and it does not explicitly distinguish itself from get_notification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives parameter-based mode guidance: 'With appId only' versus 'With productId or platforms.' However, it does not say when to use this tool instead of siblings like get_notification or coming_up, so usage is implied rather than fully specified.

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

All Hailbell 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