HacknPlan MCP

update_webhook

Partially update a webhook's configuration, such as URL, events, or secret, for a HacknPlan project. Use this tool to modify specific fields without affecting others.

Instructions

Partially update a webhook (PATCH)

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": {
      "projectId": "<projectId>",
      "webhookId": "<webhookId>"
    },
    "name": "update_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No
`events`	No
`secret`	No
`projectId`	Yes
`webhookId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions PATCH without explaining effects on missing fields, authentication, or idempotency. Bare minimum.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but fails to convey necessary details. Could be expanded without losing brevity.

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

Completeness2/5

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

Given sibling tools for creation and full replacement, this description minimally sets it apart but omits required fields and update behavior. Incomplete for an agent to use effectively.

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

Parameters1/5

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

Schema description coverage is 0%, yet the tool description adds no parameter explanations. For 5 parameters, this is insufficient. Agent must guess the meaning of url, events, secret.

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?

Clearly specifies the verb 'update' and resource 'webhook', plus indicates partial update via PATCH. Distinguishes from siblings like replace_webhook which likely does full replacement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus replace_webhook or create_webhook. Absence of any usage context makes it hard for an AI agent to decide correctly.

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

Deploy Server