Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update a webhook endpoint

update_webhook_endpoint
Destructive

Update an existing Kit webhook endpoint by changing its URL, name, subscribed events, or active/disabled status; confirmation is required.

Instructions

Update a webhook endpoint. May affect delivery, audience membership, published data or irreversible state. Requires confirm=true. Webhook response secrets are redacted; new signing secrets are saved only to a private local file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
nameNo
eventsNo
statusNoEndpoint status. One of: `active`, `disabled`.
accountNoNamed private account from KIT_ACCOUNTS. Defaults to KIT_DEFAULT_ACCOUNT or the first configured account.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete JSON body instead of individual body flags. Supports nullable fields and nested bulk structures. Cannot be combined with body flags or payload_file.
descriptionNo
payload_fileNoLocal JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.
webhook_endpoint_idYesPositive webhook endpoint id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv3.0.0
    • addedInput schema / $defs
      Added value: +{
+  "events": {
+    "description": "Event types this endpoint subscribes to (e.g. `subscriber.created`). On update, the list supplied here replaces the endpoint's full subscription list.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for audience/delivery changes, publishing, destructive operations and signing-secret changes. Use only for an action requested by the user."New value: +"Set true only when the user asked for exactly this action."
    • addedInput schema / properties / events / $ref
      Added value: +"#/$defs/events"
    • removedInput schema / properties / events / description
      Removed value: -"Event types this endpoint subscribes to (e.g. `subscriber.created`). On update, the list supplied here replaces the endpoint's full subscription list."
    • removedInput schema / properties / events / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / events / type
      Removed value: -"array"
    • addedInput schema / properties / payload / properties / events / $ref
      Added value: +"#/$defs/events"
    • removedInput schema / properties / payload / properties / events / description
      Removed value: -"Event types this endpoint subscribes to (e.g. `subscriber.created`). On update, the list supplied here replaces the endpoint's full subscription list."
    • removedInput schema / properties / payload / properties / events / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / payload / properties / events / type
      Removed value: -"array"
  2. First observedv2.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), it adds genuinely useful behavior: the confirm gate, that changes may be irreversible, that response secrets are redacted, and that new signing secrets land in a private local file. Consistent with the declared annotations.

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

Conciseness4/5

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

Three short sentences, front-loaded with the purpose and the confirm requirement. The 'delivery, audience membership, published data or irreversible state' clause is somewhat scattershot boilerplate but still earns its place as a caution.

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?

For a destructive, non-idempotent 10-parameter mutation with no output schema, the description covers the safety profile, the confirm gate, and the unusual secret-file behavior. Idempotency and partial-update semantics are left to the schema but are not critical omissions.

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 coverage is 60% with 10 parameters including nested payload/payload_file. The description touches only confirm and secret handling, adding little beyond the schema on the body-vs-flags conflict or the events-replacement semantics that matter most here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource ('Update a webhook endpoint') and is distinguishable from siblings like create_webhook_endpoint, delete_webhook_endpoint and rotate_webhook_secret by name alone. It does not explicitly name which sibling to prefer for related operations, so it stops short of 5.

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

Usage Guidelines3/5

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

It gives a prerequisite ('Requires confirm=true') and warns of side effects, which implies cautious use, but never states when to update versus rotate the secret, revoke a secret, or delete the endpoint. Usage context is implied rather than explicit.

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

Deploy Server

Other Tools