GrowSurf

Update Campaign Reward

growsurf_update_campaign_reward

DestructiveIdempotent

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

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`	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
`imageIconKey`	No	The starter icon shown for the reward, or `null` when `imageUrl` is your own image. Participant pages draw this icon in your program's accent color. Also set `imageUrl` to the icon's image so the iOS and Android SDKs can show it. Sending `imageUrl` without `imageIconKey` clears it.
`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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / imageIconKey

Added value: +{
+  "description": "The starter icon shown for the reward, or `null` when `imageUrl` is your own image. Participant pages draw this icon in your program's accent color. Also set `imageUrl` to the icon's image so the iOS and Android SDKs can show it. Sending `imageUrl` without `imageIconKey` clears it.",
+  "enum": [
+    "GIFT_1",
+    "GIFT_2",
+    "GIFT_3",
+    "GIFT_4",
+    "GIFT_5",
+    "GIFT_6",
+    "GIFT_CARD",
+    "CASH",
+    "COIN",
+    "CARD",
+    "STAR_1",
+    "STAR_2",
+    "STAR_3",
+    "TROPHY",
+    "CROWN",
+    "SEAL",
+    "HEART_1",
+    "HEART_2",
+    "TAG",
+    "DIAMOND",
+    "CONFETTI",
+    "ROCKET",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedOct 8, 2026

TDQS

B3.1/5.0

Behavior3/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 usefully adds that type is immutable and how targeting resolves, but for a 24-param destructive update it says nothing about partial-update semantics (which fields are overwritten vs. left intact), which matters given the destructive hint.

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 short sentences, each earning its place, with the primary action and targeting rule front-loaded. No filler or redundancy.

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?

An output schema exists, so return values need no explanation. However, for a 24-param destructive mutation with 25% schema coverage, the description omits partial-update behavior, required-field guidance, and side effects, leaving an agent under-informed.

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 25% across 24 parameters. The description clarifies campaignRewardId's key format and campaignId's fallback behavior, but the vast majority of parameters (limit, order, metadata, commissionStructure, value, etc.) get no added meaning from the prose, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update an existing campaign reward (reward config)') and adds the reward key format and immutability constraint. This clearly separates it from create/delete/list siblings by the word 'existing', though it never names an alternative tool explicitly.

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?

Implies usage context (updating an already-configured reward) and explains the campaignId targeting default, but never states when to reach for this tool versus create_campaign_reward or delete_campaign_reward, nor any prerequisites.

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

All GrowSurf tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.