CatchAll

Trigger Webhook

trigger_webhook

Manually trigger webhook delivery for a resource (job/monitor/monitor_group).

Use when:

You want to (re-)send a webhook delivery on demand instead of waiting for the automatic dispatch — e.g. to replay a missed or failed delivery.

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": {
      "webhook_id": "<webhook_id>",
      "resource_type": "<resource_type>",
      "resource_id": "<resource_id>"
    },
    "name": "trigger_webhook"
  }
}

Input Schema

Name	Required	Description
`job_id`	No	Optional job ID whose payload should be delivered (e.g. a specific monitor run's job). If omitted, the API picks the resource's payload itself.
`api_key`	No	CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var.
`webhook_id`	Yes	The webhook ID to deliver through.
`resource_id`	Yes	The ID of the job/monitor/monitor_group to trigger delivery for.
`resource_type`	Yes	Resource type: 'job', 'monitor', or 'monitor_group'.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 14, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the core action (manually trigger webhook delivery) and the intent (on-demand replay), but it does not disclose potential side effects (e.g., whether this creates a new history entry, idempotency, or rate limits) or any prerequisites beyond what the schema already shows. This is acceptable for a simple trigger but not fully transparent.

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 exceptionally concise: one sentence defining the action and a short 'Use when' list. It is front-loaded with the purpose and contains no filler. Every word earns its place.

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

Completeness4/5

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

The tool is simple, has a well-documented schema, and an output schema exists (so return values need no explanation). The description covers the purpose, usage context, and resource types. It does not mention potential prerequisites like needing an existing webhook assignment, but that is implied by the required webhook_id. Overall, it is sufficiently complete for an agent to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, with each parameter having a clear description (e.g., resource_type enumerated, job_id optional). The description adds no parameter-specific details, but the schema fully documents them, so the baseline of 3 is appropriate.

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 clearly states a specific verb (trigger) and resource (webhook delivery for a resource), and explicitly scopes the resource types to job/monitor/monitor_group. It distinguishes itself from siblings like test_webhook (which tests) and get_webhook_history (which retrieves) by focusing on manual delivery triggering.

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?

The description provides explicit when-to-use guidance ('Use when: You want to (re-)send a webhook delivery on demand instead of waiting for the automatic dispatch') with a concrete example (replay missed/failed delivery). However, it does not mention when not to use it or name alternative sibling tools, so it misses the 'when-not/alternatives' aspect for a top score.

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

All CatchAll 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.