Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Update Webhook

growsurf_update_campaign_webhook
DestructiveIdempotent

Updates a GrowSurf campaign webhook by ID, changing only the fields you provide such as payload URL, events, enabled status, or write-only secret.

Instructions

Update a webhook on your GrowSurf program by id (webhookId is primary for the program's primary webhook). Only the fields you send are changed. secret is write-only and never returned. A program can have only one saved Bask Health webhook across all bask.ninja hosts and paths, including disabled webhooks. An update that leaves more than one Bask Health webhook returns 400. A concurrent change to webhook settings can return 409; reload the webhooks before retrying. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

NameRequiredDescriptionDefault
eventsNoReplacement event list. Events must be ones the program type offers; an event this webhook already has on is also accepted.
secretNoWrite-only.
isEnabledNo
webhookIdYes
campaignIdYesTarget program id for this call: the `id` returned by `growsurf_list_campaigns`, not the program name or a share URL. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server.
payloadUrlNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.33
    • changedInput schema / properties / campaignId / description
      Previous value: -"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."New value: +"Target program id for this call: the `id` returned by `growsurf_list_campaigns`, not the program name or a share URL. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."
  2. Changed1 schema field changedv0.19.27
    • addedInput schema / properties / events / description
      Added value: +"Replacement event list. Events must be ones the program type offers; an event this webhook already has on is also accepted."
  3. Changed2 schema fields changedv0.19.15
    • addedInput schema / properties / campaignId / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
      -  "webhookId"
      -]New value: +[
      +  "webhookId",
      +  "campaignId"
      +]
  4. Changed1 schema field changedv0.19.9
    • changedInput schema / properties / campaignId / description
      Previous value: -"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Pass the `id` returned by growsurf_create_campaign to configure or operate a program you just created, without restarting the server."New value: +"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."
  5. Changed1 schema field changedv0.14.0
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "payloadUrl"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "events"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "secret"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "isEnabled"
      +    ]
      +  }
      +]
  6. First observedv0.12.2

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: a domain constraint (only one saved Bask Health webhook across bask.ninja hosts, including disabled ones), the resulting 400 on violation, and a 409 concurrency path with reload-before-retry guidance. What it omits is the destructive side implied by destructiveHint=true — that the events list is a wholesale replacement and what happens to events not resent.

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?

Front-loaded with the addressing rule, then patch semantics, then constraints and error codes — a sensible order with no filler sentences. The Bask Health uniqueness sentence is verbose but carries operational value, so it earns its place.

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?

With an output schema present, return values need not be explained, and the annotations already cover safety and idempotency; the description focuses on targeting, constraints, and failure modes, which is the right allocation. It is not fully complete because it leaves payloadUrl semantics and the event-replacement behavior undiscussed for a destructiveHint mutation.

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 only 50%, so the description must compensate; it does so for webhookId (the 'primary' alias, undocumented in the schema), secret (write-only, never returned), and campaignId defaulting. However payloadUrl and isEnabled receive no description-level meaning in either place, leaving real gaps for a mutation call.

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?

States a specific verb (update) and resource (webhook) scoped to a program, plus the addressing scheme: webhookId, with the literal 'primary' accepted for the program's primary webhook. An agent can distinguish this from growsurf_create_campaign_webhook or growsurf_delete_campaign_webhook purely from the text.

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

Usage Guidelines4/5

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

Explicitly frames the call as a partial update ('Only the fields you send are changed') and specifies the target resolution rule (campaignId if passed, else the GROWSURF_CAMPAIGN_ID default). It does not name sibling tools or state when to create a webhook instead of updating one, so it falls short of a full when/when-not rubric.

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