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 for languages and flags. Send only fields to change; omitted values stay, arrays replace fully, and language features need Business plan.

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. Turning languages on, and any change while they are on (including turning them off or changing showFlags), requires the Business plan or higher and returns a 403 otherwise. Translations are managed in the GrowSurf dashboard, not through this tool. Targets campaignId if supplied, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON 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

TableJSON 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.2/5.0

Behavior5/5

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

Annotations already declare destructive/idempotent/openWorld, but the description adds substantial behavior beyond them: patch semantics (only supplied fields change, omitted fields retained, arrays replace wholesale), the base-language-drop and duplicate-collapse rules, `[]` to disable languages, and a hard plan gate that returns 403 without the Business plan. That is exactly the kind of auth and mutation detail the annotations cannot carry.

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 action and target, then dense with only information-bearing sentences about merge behavior, language handling, and the plan gate. It runs long, but nearly every clause carries a rule the agent needs; nothing is 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?

For a nested-object mutation with an output schema present, the description covers merge semantics, language edge cases, targeting, and plan gating, so return values need not be explained. The one remaining gap is that it never points the agent to `growsurf_get_campaign_options` to discover the available top-level option fields.

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% (the `fields` object is undocumented in the schema), so the description must compensate, and it does: it defines `fields` as the existing nested shape and details `languages.additionalLanguages` and `languages.showFlags` semantics. It still does not enumerate the full set of option fields, so it is strong but not exhaustive.

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 and resource: 'Update the Options tab configuration for your GrowSurf program under `fields`'. This scope implicitly separates it from the many other update_campaign_* siblings (design, emails, installation) and from the generic update_campaign, though no sibling is named explicitly, so it falls short of the top band.

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 a clear when-not-use exclusion: translations are managed in the dashboard, not through this tool. It also frames the targeting rule (`campaignId` else `GROWSURF_CAMPAIGN_ID`). It does not route the agent between this tool and `growsurf_update_campaign` or `growsurf_get_campaign_options`, so it stops short of full alternative guidance.

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

Deploy Server