Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_webhook

Idempotent

Update a webhook's endpoint, events, or status to redirect deliveries, modify subscriptions, or reactivate suspended webhooks.

Instructions

Change a webhook's endpoint, event subscription, or delivery status.

Update any combination of the destination endpoint, the events list, and the status. Setting status='active' re-enables a webhook ClickUp suspended after repeated delivery failures. ClickUp treats these fields as a full replacement, so to preserve the current endpoint/events while flipping status, re-supply them (read the current values from clickup_get_webhooks).

When to Use:

  • To re-point a webhook at a new URL, or to broaden/narrow its events.

  • To reactivate a hook that stopped firing (status='active').

When NOT to Use:

  • To register a brand-new webhook — use clickup_create_webhook.

  • To remove a webhook entirely — use clickup_delete_webhook.

Returns: A confirmation naming the webhook id and the fields that changed.

Examples:

  • params = {"webhook_id": "e50...", "status": "active"}

  • params = {"webhook_id": "e50...", "endpoint": "https://x.io/hook2", "events": ["*"]}

Error Handling: 400 → invalid endpoint/event; 404 → unknown webhook id. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond annotations (non-read-only, idempotent, non-destructive), description reveals full replacement semantics, re-enable behavior for suspended webhooks, and error handling (400/404). No contradictions.

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?

Well-structured with sections for purpose, usage, returns, examples, and error handling. Every sentence is informative; no redundancy.

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?

Covers return format ('confirmation naming webhook id and changed fields'), error cases, prerequisites (use get_webhooks to read current values), and examples. Output schema exists but description still provides clarity.

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 already describes parameters (events, status, endpoint, webhook_id). Description adds value by explaining replacement behavior and need to re-supply unchanged fields, though examples and prose reinforce schema info.

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?

Description clearly states 'Change a webhook's endpoint, event subscription, or delivery status' with specific verb and resource. Differentiates from siblings by naming clickup_create_webhook and clickup_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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When to Use' and 'When NOT to Use' sections with specific scenarios like re-pointing a webhook or reactivating a suspended one. Provides alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/trustxai/clickup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server