GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Update Program Options

growsurf_update_campaign_options

DestructiveIdempotent

Update GrowSurf campaign Options configuration by sending only the fields to change; omitted values stay, arrays replace, and language or notification email settings are adjusted.

Instructions

Update the Options tab configuration for your GrowSurf program under fields, in its existing nested shape. Only supplied fields change; omitted fields retain their existing values and arrays replace wholesale. languages.additionalLanguages takes the full list of extra languages; send [] to turn them off. The base language is dropped from that list and duplicates collapse. languages.showFlags shows or hides the flag next to each language name. languages.flagCountries picks the flag for a language that offers more than one, such as { "en": "GB" }; null restores the default flag. Turning on languages.additionalLanguages returns 403 if your account does not include additional languages. While any are on, every languages change, including turning them off, returns the same 403. Translations are managed in the GrowSurf dashboard, not through this tool. notificationEmails.recipients needs at least one valid email address. 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_options"
  }
}

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/5.0

Behavior5/5

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

Goes well past the annotations by disclosing merge-vs-replace behavior, the `403` failure mode for additional languages (including that it persists for *every* languages change while any are on), and the recipient validation requirement. These are exactly the non-obvious consequences an agent needs before issuing a destructiveHint=true write.

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 action and the merge rule, then proceeds through each nested field in order with no filler sentences. It is dense but every clause carries a rule, though the run of dotted field paths would scan faster as a list.

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 nested-object mutation with a partial-update contract, this covers semantics, error cases, targeting, and out-of-scope concerns (translations). The one omission is direction to growsurf_get_campaign_options to learn the "existing nested shape" the description assumes the agent already knows.

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 only 50% and `fields` is a bare `additionalProperties: true` object, so the description carries nearly the whole burden — and does, spelling out `languages.additionalLanguages`, `showFlags`, `flagCountries` with an example value, and `notificationEmails.recipients`. It also clarifies campaignId's env-var fallback. A 5 is withheld only because the set of valid top-level `fields` keys is still open-ended.

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?

Opens with a specific verb+resource+location: "Update the Options tab configuration for your GrowSurf program under `fields`", which separates it from update_campaign, update_campaign_design, and update_campaign_emails. It stops short of naming the read counterpart (growsurf_get_campaign_options) as the way to discover the existing shape, so the boundary is inferred rather than stated.

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?

Gives strong operational context — only supplied fields change, arrays replace wholesale, `null` restores the default, translations must be edited in the dashboard instead. What it never does is state when to reach for this tool versus the sibling update_* tools, or suggest reading options first; the agent must infer usage from the semantics.

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

Deploy Server