GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Update Program Installation

growsurf_update_campaign_installation

DestructiveIdempotent

Update a GrowSurf program's Installation configuration by patching only supplied fields, such as Share URL, allowed URLs, and signup settings; omitted fields stay unchanged.

Instructions

Update the Installation tab configuration for your GrowSurf program under fields. Only supplied fields change; omitted fields retain their existing values and arrays replace wholesale. allowedUrls includes permitted browser origins such as http://localhost:3000. An origin missing from both shareUrl and allowedUrls can return 403. Referral links already shared point at the current shareUrl. Replacing an existing Share URL requires the customer's explicit approval and replaceExistingShareUrl: true; otherwise the patch is refused. Targets campaignId if supplied, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema

Name	Required	Description
`fields`	Yes	Installation fields to patch. Common keys include `shareUrl`, `allowedUrls`, `signupEvent`, `referralTrigger`, `signup`, and `instructionSelections`. Arrays replace wholesale.
`campaignId`	No	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.
`replaceExistingShareUrl`	No	Set this to `true` only after the customer confirms they want a different landing page. Without it, a patch that would replace a Share URL that is already set is refused.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.19.9Oct 3, 2026

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."

Changed1 schema field changedv0.19.8Oct 1, 2026

changedInput schema / properties / fields / properties / allowedUrls / description

Previous value: -"Every browser origin allowed to use the program, including local and staging origins. Send the full array because arrays replace wholesale."New value: +"Every browser origin allowed to use the program, including local and staging origins. Send the full array because arrays replace wholesale. Known shared-platform root domains, such as `github.io`, do not grant access. Add your site's hostname, such as `https://piedpiper.github.io`, or a domain you own. Path-based shared hosts, such as `unbouncepages.com`, require a domain you own."

Changed2 schema fields changedv0.19.7Sep 30, 2026

changedInput schema / properties / fields / description

Previous value: -"Installation fields to patch. Common keys include `shareUrl`, `allowedUrls`, `signupEvent`, `referralTrigger`, and `signup`. Arrays replace wholesale."New value: +"Installation fields to patch. Common keys include `shareUrl`, `allowedUrls`, `signupEvent`, `referralTrigger`, `signup`, and `instructionSelections`. Arrays replace wholesale."

addedInput schema / properties / fields / properties / instructionSelections

Added value: +{
+  "additionalProperties": true,
+  "description": "Guide choices. Send only the choices to change.",
+  "properties": {
+    "mobileAttributionProvider": {
+      "enum": [
+        "branch",
+        "appsflyer",
+        "adjust",
+        "singular",
+        "other"
+      ],
+      "type": "string"
+    },
+    "platform": {
+      "enum": [
+        "web",
+        "ios",
+        "android"
+      ],
+      "type": "string"
+    },
+    "stepProviders": {
+      "additionalProperties": true,
+      "description": "Selected method for each guide step. Available keys depend on program type.",
+      "properties": {
+        "step2Affiliate": {
+          "enum": [
+            "stripe",
+            "chargebee",
+            "recurly",
+            "restApi"
+          ],
+          "type": "string"
+        },
+        "step2Referral": {
+          "enum": [
+            "restApi",
+            "zapier",
+            "stripe",
+            "chargebee",
+            "recurly",
+            "paypal",
+            "hubspot",
+            "salesforce"
+          ],
+          "type": "string"
+        },
+        "step2Signup": {
+          "enum": [
+            "restApi",
+            "javascript"
+          ],
+          "type": "string"
+        },
+        "step3Affiliate": {
+          "enum": [
+            "paypal",
+            "wise"
+          ],
+          "type": "string"
+        },
+        "step3Referral": {
+          "enum": [
+            "webhooks",
+            "zapier",
+            "paypal",
+            "tangocard",
+            "stripe",
+            "chargebee",
+            "recurly"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv0.14.0Sep 10, 2026

addedInput schema / properties / replaceExistingShareUrl

Added value: +{
+  "description": "Set this to `true` only after the customer confirms they want a different landing page. Without it, a patch that would replace a Share URL that is already set is refused.",
+  "type": "boolean"
+}

First observedv0.12.2Aug 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructive/idempotent/openWorld, and the description adds real behavioral context on top: merge-vs-replace patch semantics, the 403 outcome when an origin is missing from shareUrl/allowedUrls, the effect on already-shared referral links, and the explicit-approval guard that causes the patch to be refused. This is materially more than the annotations convey.

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 core purpose, then each subsequent sentence carries a distinct constraint (merge semantics, origin rules, 403, approval guard, targeting default) with no filler. Slightly dense, but nothing is redundant.

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?

For a nested-object patch tool with an output schema already covering return values, the description supplies everything an agent needs: mutation semantics, the approval gate, error conditions, and default targeting. No meaningful gap remains.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: allowedUrls origins with a concrete example, the 403 consequence of omitting an origin, the wholesale array-replacement rule, and the campaignId fallback to GROWSURF_CAMPAIGN_ID.

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 and resource ('Update the Installation tab configuration for your GrowSurf program under `fields`'), and the scoping to the Installation tab cleanly separates it from siblings like growsurf_update_campaign_options, growsurf_update_campaign_design, and the read-only growsurf_get_campaign_installation.

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?

Gives clear operational conditions: only supplied fields change, arrays replace wholesale, and replacing a Share URL requires customer approval plus `replaceExistingShareUrl: true` or the patch is refused. It does not explicitly point to alternatives such as the get_campaign_installation reader, so it stops short of a 5.

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

Deploy Server