Relinta

List webhook deliveries

listWebhookDeliveries

Read-onlyIdempotent

List webhook deliveries

Returns up to 100 newest deliveries for one endpoint. Filter by current delivery status and pass pagination.nextCursor unchanged to read the next page. A delivery may have multiple automatic or manual attempts; use getWebhookDelivery for the payload and attempt history.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "listWebhookDeliveries"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`query`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`headers`	Yes
`httpStatus`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), and the description adds real behavior beyond them: a 100-item cap, newest-first ordering, and the fact that a delivery can have multiple automatic or manual attempts. It does not mention rate limits or retention windows, which would be the next useful disclosures.

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?

Three tight sentences with the scope front-loaded, then paging/filtering mechanics, then the sibling hand-off. Nothing is repeated from the title and no sentence is filler.

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?

Given an output schema (so return values need no explanation) and annotations that carry the safety profile, the description supplies everything else needed to call it correctly: page size, ordering, filterable status, pagination contract, and the relationship to getWebhookDelivery.

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?

Adds meaning beyond the schema by explaining that the cursor is opaque and must be passed unchanged and that the status filter matches the delivery's *current* status. Minor friction: the description calls the value 'pagination.nextCursor' while the schema parameter is named 'cursor', which could momentarily confuse an agent mapping response fields to request fields.

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 plus the scope: 'Returns up to 100 newest deliveries for one endpoint.' It explicitly differentiates from the sibling getWebhookDelivery, which handles payload and attempt history, so an agent can choose without opening either 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?

Gives clear routing guidance ('use getWebhookDelivery for the payload and attempt history') and explains the status filter and cursor pass-through. It does not state when listing is unnecessary (e.g., when a delivery id is already known), so the exclusion side is only implied.

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

All Relinta tools Inspect

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

Need Help?