CatchAll (by NewsCatcher)

Official

by Newscatcher

Overview Schema Source Related Servers Discussions Admin

Python

Remote

remove_webhook_resource

Unmap a job, monitor, or monitor group from a webhook to stop it from triggering notifications for that resource.

Instructions

Unmap a resource from a webhook.

Use when:

You want to stop a webhook from firing for a specific job or monitor.

Input Schema

TableJSON Schema

Name	Required	Description
`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 detach the resource from.
`resource_id`	Yes	The ID of the mapped job/monitor/monitor_group.
`resource_type`	Yes	Resource type: 'job', 'monitor', or 'monitor_group'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It states the action ('unmap', 'stop') but lacks details on side effects, permissions, reversibility, or error handling.

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?

Extremely concise: two sentences plus a usage clause. No unnecessary words, front-loads the core action.

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?

Given the tool's simplicity, presence of output schema, and full parameter descriptions, the description covers purpose and usage adequately. Lacks some behavioral details but not critical for a removal operation.

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 describes all parameters thoroughly (100% coverage). Description adds minimal extra context beyond schema, aligning with baseline for high schema coverage.

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 uses a specific verb 'Unmap' and resource 'resource from a webhook', clearly distinguishing from sibling tools like 'assign_webhook_resource' and 'delete_webhook'.

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 a clear 'Use when' clause specifying the context: stop a webhook from firing for a specific job or monitor. Does not explicitly exclude alternatives but context is sufficient.

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

Deploy Server