GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

growsurf_update_campaign_installation

DestructiveIdempotent

Patch GrowSurf program installation configuration, updating only the fields you send. Change allowed origins or Share URL after customer confirmation.

Instructions

Update the Installation tab configuration for your GrowSurf program. Only the fields you send are changed; anything you leave out is untouched (arrays replace wholesale). To let GrowSurf run on another origin, such as http://localhost:3000, add that origin to allowedUrls and preserve the rest of the array; a browser origin missing from both shareUrl and allowedUrls can return 403. Leave shareUrl out of the patch unless the customer asked for a different landing page: every referral link already shared points at the current one. A patch that would replace a Share URL that is already set is refused until you confirm it with the customer and resend with replaceExistingShareUrl: true. Fetch the tab first, then pass just the fields you want to change under fields. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema

Name	Required	Description
`fields`	Yes	Installation fields to patch. Common keys include `shareUrl`, `allowedUrls`, `signupEvent`, `referralTrigger`, and `signup`. Arrays replace wholesale.
`campaignId`	No	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.
`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.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.7/5.0

Behavior5/5

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

Annotations already mark destructiveHint=true and idempotentHint=true, and the description significantly extends this: it spells out partial patch semantics, wholesale array replacement, the 403 risk for origins missing from allowedUrls/shareUrl, and the refusal behavior for replacing an existing shareUrl. This is rich behavioral disclosure that goes well beyond the structured data and never contradicts it.

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?

The description is longer than average, but each sentence introduces a necessary nuance around patch semantics, allowedOrigins, shareUrl, and the confirm flag. It is front-loaded with the purpose and reads in a natural cause-and-effect order. A sentence or two could be tightened, but the length is justified by the risk profile.

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?

Given the tool has an output schema and high schema coverage, the description covers all high-risk operational aspects: array replacement, 403 behavior, shareUrl safety, partial patch behavior, and campaign targeting. There is nothing critical an agent needs to know for safe invocation that is missing.

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

Parameters5/5

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

Although the input schema is fully described, the function description adds meaning: it clarifies that fields is a partial-patch payload, allowedUrls must be sent as a full array, shareUrl replacement is blocked unless replaceExistingShareUrl is true, and campaignId overrides GROWSURF_CAMPAIGN_ID. This is substantial additional semantics that helps an agent use the parameters correctly.

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?

The description opens with a specific verb and resource: 'Update the Installation tab configuration for your GrowSurf program.' This clearly distinguishes it from siblings like growsurf_update_campaign, growsurf_update_campaign_design, and other update-* tools, which target different configuration surfaces. The scope is unambiguous.

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?

It gives strong procedural guidance: fetch the tab first, patch only changed fields, and preserve array contents. It explains when to avoid touching shareUrl and when to set replaceExistingShareUrl. It doesn't literally name alternative sibling tools for exclusion, but the 'Installation tab' framing, plus the 'fetch first' step, makes the usage context very clear.

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

Deploy Server