garu-mcp

Official

Overview Schema Source Related Servers Discussions Admin

list_webhook_events

Audit webhook deliveries by listing events filtered by status, type, or endpoint. Ideal for confirming if a customer's endpoint received a specific event.

Instructions

List webhook events for the authenticated seller. Filter by delivery status (pending, success, failed), by Garu event type (e.g. 'transaction.payment.paid'), and/or by the destination endpoint id. Use this to audit deliveries — the canonical 'did my customer's endpoint actually receive event X?' workflow. Newest first.

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

Input Schema

Name	Required	Description
`page`	No	Page number, default 1
`limit`	No	Items per page, default 50
`status`	No	Filter by delivery state. 'pending' = queued/awaiting retry; 'success' = endpoint returned 2xx; 'failed' = retries exhausted.
`event_type`	No	Filter by Garu event type, e.g. 'transaction.payment.paid' or 'scheduled_charge.cycle_failed'.
`endpoint_id`	No	Filter by destination endpoint id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.18.0Jul 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Since no annotations are provided, the description carries full burden. It discloses ordering ('Newest first') and explains filter options (status meanings, event type examples). Missing details on rate limits or pagination beyond order, but sufficient for common use.

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 sentences: action+resource, filter options, use case+ordering. No unnecessary words, front-loaded with essential information.

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?

No output schema, so description should explain return values. It does not describe what fields are returned or pagination details beyond ordering. Adequate but lacks return structure.

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 100% (all parameters have descriptions). The description adds context by explaining the audit purpose and giving examples (e.g., event type 'transaction.payment.paid'). This adds value beyond the schema alone.

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?

Clearly states the verb (list) and resource (webhook events) for the authenticated seller. Distinguishes from siblings like get_webhook_event (single) and retry/resend webhook event (actions).

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?

Provides explicit use case: 'audit deliveries — the canonical 'did my customer's endpoint actually receive event X?' workflow.' Lists available filters, implying when to use each. However, no explicit exclusion criteria for when not to use.

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

Deploy Server