Skip to main content
Glama
growsurf

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Webhook

growsurf_update_campaign_webhook
DestructiveIdempotent

Update a GrowSurf program webhook by ID to change its payload URL, events, secret, or enabled status. Only fields you send are modified.

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. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsNo
secretNoWrite-only.
isEnabledNo
webhookIdYes
campaignIdNoTarget program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server.
payloadUrlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Changed1 schema field changedv0.14.0
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "payloadUrl"
+    ]
+  },
+  {
+    "required": [
+      "events"
+    ]
+  },
+  {
+    "required": [
+      "secret"
+    ]
+  },
+  {
+    "required": [
+      "isEnabled"
+    ]
+  }
+]
  3. First observedv0.12.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint, and openWorldHint. The description adds genuine value beyond them: patch semantics ('Only the fields you send are changed'), the write-only, never-returned nature of `secret`, and the special 'primary' webhook id. It does not explain permission needs or why the update is flagged destructive, keeping it from a 5.

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?

Four tight sentences, front-loaded with the core action before the special-case notes. Each sentence carries distinct information (patch semantics, write-only secret, campaign targeting) with no filler.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description covers the tricky special cases (primary id, patch behavior, env fallback), leaving only the self-evident events/isEnabled/payloadUrl fields unaddressed.

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 33%, so the description must compensate. It adds meaning for webhookId ('primary'), secret (write-only), and campaignId (env fallback), but leaves events, isEnabled, and payloadUrl undocumented and does not explain the anyOf at-least-one-field requirement.

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 specific verb+resource: 'Update a webhook on your GrowSurf program by id'. An agent can tell this is the mutation counterpart to the create/delete/list/test webhook siblings. It stops short of explicitly naming those alternatives, so it is clear but not fully sibling-differentiated.

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?

The description gives no when-to-use guidance, prerequisites, or named alternatives among the webhook siblings (create/delete/test/list). Usage is only implied by the verb 'Update', with no exclusions or conditions stated.

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