GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Update Program

growsurf_update_campaign

DestructiveIdempotent

Updates a GrowSurf program's name, company details, logo, or status to publish, resume, or end it, changing only the fields you send.

Instructions

Update your GrowSurf program's (campaign's) identity and lifecycle: name, companyName, companyLogoImageUrl, and status (set IN_PROGRESS to publish/resume the program, COMPLETE to end it). Only the fields you send are changed. type, urlId, and currencyISO are immutable (currency is chosen once at program creation), so this tool does not accept them. Editor-tab config (design, emails, options, installation) is edited with the dedicated config sub-resource tools, not here. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`status`	No	Lifecycle transition. IN_PROGRESS publishes/resumes the program; COMPLETE ends it. These are the only accepted targets — DRAFT/PENDING/CANCELLED are rejected by the API.
`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.
`companyName`	No
`companyLogoImageUrl`	No

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.14.0Sep 10, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "name"
+    ]
+  },
+  {
+    "required": [
+      "companyName"
+    ]
+  },
+  {
+    "required": [
+      "companyLogoImageUrl"
+    ]
+  },
+  {
+    "required": [
+      "status"
+    ]
+  }
+]

First observedv0.12.2Aug 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: partial-update semantics ('only the fields you send are changed'), immutability of type/urlId/currencyISO, and the fact that COMPLETE ends the program. It stops short of explicitly warning that ending a program is irreversible, which keeps it from a 5.

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

Conciseness5/5

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

Front-loaded with the core purpose, then layered with status semantics, partial-update behavior, exclusions, and targeting. Every sentence carries actionable information; there is no filler or repetition of the title.

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?

An output schema exists, so return values need not be explained, and the annotations carry the destructive/idempotent profile. What remains — mutable fields, status transitions, immutability constraints, sibling routing, and target resolution — is all present, leaving no gap an agent would need to guess at.

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 description coverage is only 40%, so the description must compensate, and it does: it names all four mutable fields, explains the status enum transitions (IN_PROGRESS publishes/resumes, COMPLETE ends), and calls out three fields the tool deliberately rejects. The campaignId fallback to GROWSURF_CAMPAIGN_ID is also stated, though the description largely mirrors the schema's own note.

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 (update) and resource (GrowSurf program/campaign), enumerates the exact mutable fields, and explicitly separates itself from the editor-tab config tools handled by dedicated sub-resource siblings. An agent can distinguish it from growsurf_update_campaign_design/emails/options/installation without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly scopes when to use it (identity and lifecycle fields) and when not to (design, emails, options, installation go to the config sub-resource tools). It also explains the conditional behavior of the status parameter, giving the agent a decision rule rather than leaving it 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