GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Campaign Reward

growsurf_create_campaign_reward

Create a new GrowSurf campaign reward with a compatible type, event, value, and limits for a specified or default campaign.

Instructions

Create a new campaign reward (reward config) on your GrowSurf program. type must be compatible with the program type (affiliate programs support only AFFILIATE rewards; referral programs support the other types). Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes
`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`	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.
`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
`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.

Changed2 schema fields changedv0.19.15Oct 15, 2026
- addedInput schema / properties / campaignId / minLength
```
Added value: +1
```
- changedInput schema / required
```
Previous value: -[
-  "type"
-]New value: +[
+  "type",
+  "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."

Changed6 schema fields changedv0.19.8Oct 1, 2026

changedInput schema / properties / couponCode / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / imageUrl / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / nextMilestonePrefix / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / nextMilestoneSuffix / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / referralCouponCode / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / referralDescription / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

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

Behavior4/5

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

Annotations already declare the safety profile (not read-only, not idempotent, not destructive), lowering the bar. The description adds a genuine behavioral constraint the annotations don't carry: type/program compatibility (AFFILIATE-only for affiliate programs) and the campaignId defaulting rule. It stops short of auth requirements or failure modes, but this is solid added context.

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?

Three sentences, purpose first, then the type-compatibility rule, then the targeting rule. Nothing is redundant, though the constraint sentence is somewhat dense for the space it gets.

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

Completeness3/5

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

The output schema exists so return values needn't be explained, and the program-type rule is the single most important piece of context for this tool. But for a 23-parameter mutation tool with nested objects, the description is far from complete — it omits required pairings, the meaning of the many optional fields, and error behavior.

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?

With 23 parameters at only 22% schema description coverage, the description must carry the semantic load and does not. It explains only `type` and `campaignId`, leaving 21 parameters (including the nested value/referredValue/commissionStructure objects) undocumented in prose, so an agent gets little beyond the raw 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?

States a specific verb (create) plus resource (campaign reward / reward config) and names the parent program scope. It is trivially distinguishable from siblings like update_campaign_reward, delete_campaign_reward, and list_campaign_rewards.

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 real routing context: `type` must match the program type, and campaignId falls back to GROWSURF_CAMPAIGN_ID. However it never names the sibling tools an agent might confuse it with (update/delete/clone reward), so the when-not guidance is only implicit.

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

Deploy Server