GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Update Program Design

growsurf_update_campaign_design

DestructiveIdempotent

Update the design configuration for a GrowSurf program, covering avatars, referral page content, website widget, traffic insights, sign-in copy, and settings. Only supplied fields change.

Instructions

Update the design configuration for your GrowSurf program, including participant avatars under participantAvatarStyle, referred-visitor content such as the Claim Offer Popup and the side content of its GrowSurf page (referredExperience.offerPageDescription HTML, up to 5 offerPageSteps of { text, iconKey }, and up to 3 offerPageLinks of { text, url } where an empty url links to the Share URL), the website widget under widget (button or card, placement, timing, and visible pages), the participant Traffic report under trafficInsights, participant sign-in copy under login, payout-destination confirmation page copy under payoutDestinationConfirmation, and the participant Settings panel under participantSettings, such as the language picker's languageSectionTitle (up to 100 characters) and languageSectionInstructionsText (up to 255 characters). trafficInsights.isPublicDisplayed controls visibility; its labels cannot be blank. participantAvatarStyle accepts CHARACTERS, INITIALS, ANIMALS, or GRADIENT. visualStyle accepts GLOW, CLEAN, FLAT, ROUND, TINT, or GLASS; it sets corners, shadows, button shape and background on program pages and the GrowSurf Window. Changing it also fills theme.buttons.borderRadius and the theme.globalBoxShadow fields unless the same request sets them. Text fields use the same character limits as the dashboard Program Editor. Text the Program Editor requires, such as Window labels, button text, and status names, cannot be set to null, empty, or only spaces. Only supplied fields change; omitted fields retain their existing content and arrays replace wholesale. Targets campaignId if supplied, otherwise GROWSURF_CAMPAIGN_ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fields": "<fields>",
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_update_campaign_design"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	Yes
`campaignId`	Yes	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.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.19.15Oct 15, 2026
- addedInput schema / properties / campaignId / minLength
```
Added value: +1
```
- changedInput schema / required
```
Previous value: -[
-  "fields"
-]New value: +[
+  "fields",
+  "campaignId"
+]
```

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

First observedv0.12.2Aug 25, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the supplied annotations, the description discloses genuinely non-obvious behavior: partial-merge semantics for omitted fields, wholesale array replacement, the `visualStyle` side effect that overwrites `theme.buttons.borderRadius` and `theme.globalBoxShadow` unless set in the same request, non-blank label requirements, and per-field character limits. This is exactly the hidden-effect information an agent needs before invoking a destructive mutator.

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

Conciseness3/5

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

Content is dense and front-loaded reasonably, but it is delivered as a sprawling run-on sentence that chains a dozen unrelated field groups with commas and semicolons. The information earns its place; the packaging does not — bulleted or segmented structure would make the same constraints far easier to scan without expanding length.

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 complex nested mutation with an output schema available, the description covers targeting, merge semantics, validation constraints, and enum values comprehensively. The remaining gap is procedural rather than descriptive: it never suggests reading current state via growsurf_get_campaign_design before writing, nor mentions permission/authentication prerequisites.

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?

Schema coverage is only 50% — `campaignId` is documented but `fields` is an open object with `additionalProperties: true` and no schema description — so the description carries the burden and largely discharges it. It enumerates concrete sub-keys, allowed enum values for `participantAvatarStyle` and `visualStyle`, array size caps for `offerPageSteps`/`offerPageLinks`, and the empty-`url` share-link shortcut, which are not derivable from the schema.

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?

The description opens with a specific verb+resource ("Update the design configuration for your GrowSurf program") and enumerates the design surfaces it governs — avatars, referred-visitor experience, widget, traffic insights, sign-in copy, payout confirmation, settings. This clearly separates it from siblings like update_campaign_options or update_campaign_emails, though it never names those siblings explicitly.

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 supplies useful usage rules — only supplied `fields` change, arrays replace wholesale, and the target defaults to `GROWSURF_CAMPAIGN_ID` — which tells the agent how to call it. However, there is no guidance on when to prefer this over the adjacent tools (growsurf_update_campaign_options, growsurf_get_campaign_design, growsurf_program_design_advisor), so selection between overlapping mutators is left to inference.

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

Deploy Server