Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_webhook

Register a webhook to push ClickUp events to your HTTPS endpoint, with optional filters for specific Spaces, Folders, Lists, or Tasks.

Instructions

Register a webhook that pushes ClickUp events to your endpoint.

Subscribes an HTTPS endpoint to one or more event types across a Workspace, optionally narrowed to a single Space, Folder, List, or Task. Pass events=['*'] to receive every event. ClickUp responds with the new webhook id and a health object (status/fail_count) reflecting delivery health.

When to Use:

  • To wire ClickUp into an external system (CI, chatops, sync jobs) on task or hierarchy changes.

  • To watch a single List/Task by setting the matching location filter.

When NOT to Use:

  • To inspect or repair existing webhooks — use clickup_get_webhooks then clickup_update_webhook.

  • For one-off reads of data — call the relevant read tool directly.

Returns: A confirmation with the new webhook id, its health status, and the subscribed events.

Examples:

Error Handling: 400 → invalid/unreachable endpoint or unknown event name; 404 → unknown team/location id. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate this is not read-only and not destructive, but description adds specifics: it subscribes an endpoint, responds with webhook id and health object, and details 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?

The description is well-structured with clear sections (purpose, when to use/not use, returns, examples, error handling). No redundant information, every sentence is useful.

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 the tool's complexity, annotations, and existence of an output schema, the description covers all necessary aspects: creation, filtering, wildcard events, return fields, and error codes. No gaps.

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?

The input schema already describes each parameter, but the description adds value by showing usage examples and specifying error handling for invalid endpoint or unknown event names.

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 it registers a webhook to push events to an endpoint. It uses a specific verb ('Register a webhook') and resource ('ClickUp events'), and distinguishes from siblings like clickup_get_webhooks and clickup_update_webhook by indicating when not to use those.

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?

The description explicitly states when to use (to wire into external systems, watch single list/task) and when not to use (to inspect/repair existing webhooks, for one-off reads). It also provides concrete examples of parameters.

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