GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

growsurf_update_campaign_reward

DestructiveIdempotent

Modify an existing campaign reward's settings such as value, visibility, limits, and tax details. Specify the reward by campaignRewardId; optionally target a specific campaign.

Instructions

Update an existing campaign reward (reward config) on your GrowSurf program. campaignRewardId is the reward key (e.g. crew_...). The reward type is immutable. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema

Name	Required	Description
`event`	No	The referral event that earns this Campaign Reward. Use `LEAD` for a referred signup or `CONVERSION` for a qualifying action. A `LEAD` reward requires a later custom conversion trigger. Referral reward types only.
`limit`	No
`order`	No
`title`	No
`value`	No	Tax valuation for the reward (the referrer's side of a double-sided reward). `fairMarketValueUSD` is the manual fair-market value in USD (major units). `taxCharacter` is the reason the recipient earns the reward. For configurable non-commission rewards, `null` inherits the program's confirmed treatment. Commission rewards always use `NONEMPLOYEE_SERVICES`.
`imageUrl`	No
`metadata`	No
`isVisible`	No
`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.
`couponCode`	No
`description`	No
`isUnlimited`	No
`limitDuration`	No
`referredValue`	No	Tax valuation for the referred friend's side of a double-sided reward. `taxCharacter` is the reason the recipient earns the reward. For configurable non-commission rewards, `null` inherits the program's confirmed treatment. Commission rewards have no referred-friend side, so GrowSurf clears these settings. Use `PURCHASE_REBATE` only when that is the correct tax character.
`numberOfWinners`	No
`campaignRewardId`	Yes
`referralCouponCode`	No
`commissionStructure`	No	Affiliate commission structure (AFFILIATE rewards only). Provide a positive `amount` (+ optional `amountISO`) for a FIXED commission, or `percent` for a PERCENT commission. CLICK and LEAD commissions must use FIXED.
`conversionsRequired`	No
`nextMilestonePrefix`	No
`nextMilestoneSuffix`	No
`referralDescription`	No
`referredRewardUpfront`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.14.0Sep 10, 2026

addedInput schema / properties / commissionStructure / allOf

Added value: +[
+  {
+    "if": {
+      "properties": {
+        "event": {
+          "enum": [
+            "CLICK",
+            "LEAD"
+          ]
+        }
+      },
+      "required": [
+        "event"
+      ]
+    },
+    "then": {
+      "properties": {
+        "amount": {
+          "minimum": 1,
+          "type": "integer"
+        },
+        "type": {
+          "enum": [
+            "FIXED"
+          ]
+        }
+      },
+      "required": [
+        "amount"
+      ]
+    }
+  }
+]

changedInput schema / properties / commissionStructure / description

Previous value: -"Affiliate commission structure (AFFILIATE rewards only). Provide `amount` (+ optional `amountISO`) for a FIXED commission, or `percent` for a PERCENT commission."New value: +"Affiliate commission structure (AFFILIATE rewards only). Provide a positive `amount` (+ optional `amountISO`) for a FIXED commission, or `percent` for a PERCENT commission. CLICK and LEAD commissions must use FIXED."

addedInput schema / properties / commissionStructure / properties / amount / minimum
```
Added value: +1
```

addedInput schema / properties / commissionStructure / properties / event / description

Added value: +"The affiliate event that earns the commission. `CLICK` and `LEAD` must use `FIXED`."

addedInput schema / properties / event

Added value: +{
+  "description": "The referral event that earns this Campaign Reward. Use `LEAD` for a referred signup or `CONVERSION` for a qualifying action. A `LEAD` reward requires a later custom conversion trigger. Referral reward types only.",
+  "enum": [
+    "LEAD",
+    "CONVERSION"
+  ],
+  "type": "string"
+}

First observedv0.12.2Aug 25, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description discloses two important behaviors beyond what annotations provide: the reward `type` is immutable, and the call targets `campaignId` with a GROWSURF_CAMPAIGN_ID default. Since annotations already flag this as destructive and idempotent, these additions are meaningful but do not contradict the 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?

Three sentences carry all the key information with no fluff: the action and resource, the identifier meaning, the immutability constraint, and the targeting default. The most important facts are front-loaded, and every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's high complexity (23 parameters, nested objects, enums, conditional constraints), the description is far too short to guide correct invocation. It does not explain partial update semantics, whether omitted fields are preserved, or how the many optional fields interact. The output schema covers return values, but the input side remains under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 22%, and the description compensates for only two parameters: `campaignRewardId` and `campaignId`. The remaining 21 parameters, including nested objects like `value`, `referredValue`, and `commissionStructure`, receive no additional semantic guidance in the description, leaving agents to rely on an under-documented schema.

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 uses a specific verb and resource: 'Update an existing campaign reward (reward config)'. The qualifier 'existing' clearly distinguishes it from create/delete siblings, and the target resource is unambiguous. The statement that `campaignRewardId` is the reward key adds further precision.

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?

The description implies usage for updating an existing reward, but it does not explicitly state when to choose this tool over growsurf_create_campaign_reward or growsurf_delete_campaign_reward. It also omits any discussion of prerequisites or conditions that would route an agent to an alternative.

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

Deploy Server