GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Campaign Reward

growsurf_create_campaign_reward

Set up a reward configuration for a GrowSurf referral or affiliate program, choosing the reward type and defining event, value, limits, and visibility rules.

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`	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
`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.5/5.0

Behavior3/5

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

Annotations already indicate this is a mutating, non-idempotent, non-destructive operation, and the description aligns with that. The description adds useful behavioral context about program-type compatibility and campaignId fallback. It does not disclose validation side effects, auth requirements, or what happens on type mismatch, but given annotation coverage the additional context is adequate.

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 compact and front-loaded: the first sentence states the purpose, the second gives the most important constraint, and the third explains campaign targeting. Every sentence earns its place with no filler or repetition.

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?

Despite having an output schema, the tool has 23 parameters, nested objects, and many type-conditional fields, yet the description only explains two aspects. An agent would still be uncertain about which fields are required for a given reward type, how `event` relates to reward types, or what `commissionStructure` needs for AFFILIATE rewards. The description is not complete enough for correct invocation of such a complex tool.

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%, so the description must compensate. It does add meaning for `type` (compatibility with program type) and `campaignId` (default behavior), but the other 21 parameters—including `event`, `value`, `referredValue`, `commissionStructure`, `isUnlimited`, and many more—receive no description-level guidance. This is a substantial gap for a tool with many conditional fields.

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 clear verb and object: 'Create a new campaign reward (reward config) on your GrowSurf program.' This distinguishes the tool from sibling update/list/delete reward tools. The added note about type compatibility and campaignId targeting further clarifies exactly what the tool creates and where.

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 gives useful context: type must match the program type, and campaignId defaults to GROWSURF_CAMPAIGN_ID when omitted. However, it does not explicitly say when to use this tool versus update_campaign_reward or list_campaign_rewards, nor does it state exclusions or prerequisites such as needing an existing program.

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

Deploy Server