Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_webhooks

Read-onlyIdempotent

List all webhooks registered in a ClickUp workspace, including delivery health status and failure count, to audit endpoints and identify failing subscriptions.

Instructions

List the webhooks registered in a Workspace, with their delivery health.

Returns every webhook the authenticating token created for the Workspace, surfacing each hook's health.status (active / failing) and fail_count so you can spot a broken endpoint before re-pointing or re-enabling it.

When to Use:

  • To find a webhook's id before clickup_update_webhook / clickup_delete_webhook.

  • To audit which endpoints are subscribed and whether any are failing.

When NOT to Use:

  • To create a new webhook — use clickup_create_webhook.

Returns: A list of webhooks (endpoint, id, health status, events, and any location filter). Only webhooks created by the authenticating user are returned.

Examples:

  • params = {}

  • params = {"team_id": "9008", "response_format": "json"}

Error Handling: 404 → unknown team id; 401 → bad token. 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?

Annotations indicate read-only, idempotent, non-destructive. Description adds that it returns only webhooks created by the authenticating user, includes health.status and fail_count, and lists error handling (404, 401). No contradiction with annotations.

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?

Description is well-structured with sections (main purpose, when to use, when not, returns, examples, error handling). Each sentence adds value. No wasted words.

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 simplicity (2 parameters with schema descriptions) and presence of an output schema (though not shown), the description covers all necessary context: purpose, usage, return content, error handling, and examples. No gaps.

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?

The input schema already provides good descriptions for both parameters (team_id, response_format). The tool description does not add additional parameter meaning beyond what the schema states, so baseline 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 starts with 'List the webhooks registered in a Workspace, with their delivery health,' clearly stating the verb (list) and resource (webhooks). It differentiates from siblings like clickup_create_webhook and clickup_delete_webhook by specifying it lists existing webhooks and includes health status.

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: use for finding webhook IDs before update/delete, audit health; not for creation (use clickup_create_webhook). Provides clear contextual guidance.

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