GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

growsurf_update_campaign

DestructiveIdempotent

Update your GrowSurf referral program's name, company name, logo, or lifecycle status. Set IN_PROGRESS to publish/resume, COMPLETE to end. Only fields you send are changed.

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. Pass the `id` returned by growsurf_create_campaign to configure or operate a program you just created, 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.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.9/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=true, idempotent=true), the description adds meaningful behavior: partial-update semantics ('Only the fields you send are changed'), the lifecycle meanings of status values, and targeting behavior (campaignId or GROWSURF_CAMPAIGN_ID). No contradiction with annotations.

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?

The description is information-dense and every sentence earns its place: scope, update semantics, immutables, sibling routing, and target resolution. Key purpose is front-loaded in the first sentence.

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?

For a 5-parameter mutation tool with an output schema and annotations, the description covers all operationally relevant aspects: what is updated, what is immutable, what is excluded, and how the target campaign is selected. Nothing an agent needs to call it correctly is left out.

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 groups name/companyName/companyLogoImageUrl as identity fields, explains the status enum semantically, and clarifies campaignId targeting/defaulting. It does not give format constraints for companyLogoImageUrl or name, but the core meaning is conveyed.

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 your GrowSurf program's (campaign's) identity and lifecycle', then enumerates the exact mutable fields (name, companyName, companyLogoImageUrl, status). It distinguishes itself from the config-focused sibling tools by explicitly stating that editor-tab configuration is handled by dedicated config sub-resource tools, not this one.

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?

It gives explicit when-not guidance: config fields (design, emails, options, installation) should go to dedicated config sub-resource tools. It also specifies lifecycle usage: IN_PROGRESS publishes/resumes, COMPLETE ends, and immutable fields (type, urlId, currencyISO) are not accepted.

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

Deploy Server