Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List webhook deliveries

list_webhook_deliveries
Read-only

List recent webhook delivery attempts with pending, success, or failed status to debug failed or missing webhook events.

Instructions

List recent webhook delivery attempts (status: pending/success/failed) for debugging.

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_webhook_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / default
      Removed value: -50
  2. First observedv0.73.1

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true and destructiveHint=false annotations already establish this is a safe read, so the description's job is narrower. It adds the status vocabulary and the 'recent' scoping notion, but never defines how 'recent' is bounded, whether results are paginated, or whether delivery payloads/errors are included.

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?

One compact sentence with the resource and the status filter front-loaded and no wasted words. It is efficient, though the parenthetical could have been spent on limit or pagination behavior instead.

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?

For a simple read-only list tool with one optional parameter and no output schema, the definition is minimally sufficient. It still leaves an agent guessing about default page size, ordering, and what a delivery record contains, which matters for a debugging tool whose value is in the returned detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'limit' has 0% schema description coverage, so the description carries the full burden and does not meet it. The word 'recent' vaguely gestures at result-count behavior but gives no default, maximum, or ordering semantics for limit, adding essentially no meaning beyond the schema.

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 gives a specific verb+resource ('List recent webhook delivery attempts') and narrows scope with the enumerated statuses (pending/success/failed), which clearly separates it from list_webhooks or redeliver_webhook_delivery. It does not explicitly name or contrast a sibling, so it falls short of a 5.

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?

'for debugging' gives an implied use context, which is more than nothing. However, there is no statement of when not to use it versus list_webhooks (configuration vs. delivery history) or redeliver_webhook_delivery (retry), leaving the agent to infer routing.

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

Deploy Server

Other Tools