GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

growsurf_get_campaign_options

Read-onlyIdempotent

Retrieve the full Options tab configuration for a GrowSurf program to review referral triggers, anti-fraud settings, affiliate enrollment, and notifications before updating.

Instructions

Fetch the Options tab configuration for your GrowSurf program (referral triggers, anti-fraud lists and toggles, affiliate enrollment and application review, notifications, and other behavior options). Returns the full object with every field and its current value, the same shape you send back on update. autoFulfillRewards: false permits manual fulfillment and does not prove that any reward went undelivered. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`fraud`	No	Anti-fraud settings: `blockedEmails`/`blockedIps`/`blockedCountries` and matching allow lists, `blockBurnerEmails`, `blockDataCenterIps`, `blockHighRiskReferrers`, `autoBlockHighRiskIps`, per-IP signup rate limits, and `recaptcha`.
`autoBlockFraud`	No	Automatically block signups flagged as high fraud risk.
`rewardEvidence`	No	What this response establishes about rewards. Combine with other reads; unknown here does not override evidence elsewhere.
`payoutThreshold`	No	Affiliate programs only. Minimum payout in minor currency units (e.g. cents). `0` or `null` means no minimum.
`taxDocumentation`	No	Affiliate programs only. Company billing details (name, address, VAT number) used on affiliate payout invoices and for VAT handling.
`autoFulfillRewards`	No	Referral programs only. Automatically mark earned rewards as fulfilled. `false` permits manual fulfillment and does not establish a delivery failure.
`notificationEmails`	No	Owner notification settings: `recipients` plus per-event `events` toggles.
`blockPaidAdsTraffic`	No	Do not attribute referrals from visitors who arrived through paid ads.
`enforceGdprCompliance`	No	Store only the minimum participant data (no IP addresses, fingerprints, or mobile instance ids).
`requireParticipantAuth`	No	Require returning participants to authenticate. Affiliate programs require `true`.
`affiliateApplicationMode`	No	Affiliate programs only. How public signups join the program. `OPEN_ENROLLMENT` enrolls them directly; `MANUAL_REVIEW` collects an application you approve or deny; `AUTO_APPROVE` collects the application and approves it immediately. A reviewed mode requires the program's published application page. Enrollment through the API, CSV import, dashboard, or invites is never blocked by this setting.
`referralCookieWindowDays`	No	How long a referral-link click is remembered in the visitor's browser, in days.
`referralCreditWindowDays`	No	How long a referred friend has to complete the qualifying action, in days. `null` means the credit never expires.
`requireManualFraudApproval`	No	Flag suspected fraud for review instead of blocking signups automatically.
`requireManualRewardApproval`	No	Referral programs only. Hold each earned reward for manual approval before it unlocks.
`affiliateReapplicationPolicy`	No	Affiliate programs only. Whether a denied applicant may apply again. `AFTER_COOLDOWN` (the default) allows a new application once `affiliateReapplicationCooldownDays` has passed; `DISABLED` never allows one.
`affiliateReapplicationCooldownDays`	No	Affiliate programs only. How many days a denied applicant waits before they can apply again (1-365, default 30). Only used when `affiliateReapplicationPolicy` is `AFTER_COOLDOWN`.
`affiliateApplicationReviewEstimateBusinessDays`	No	Affiliate programs only. Optional review-time expectation shown to pending applicants, in business days (1-60). `null` clears it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.14.0Sep 10, 2026

changedOutput schema / properties / autoFulfillRewards / description

Previous value: -"Referral programs only. Automatically mark earned rewards as fulfilled."New value: +"Referral programs only. Automatically mark earned rewards as fulfilled. `false` permits manual fulfillment and does not establish a delivery failure."

addedOutput schema / properties / rewardEvidence

Added value: +{
+  "description": "What this response establishes about rewards. Combine with other reads; unknown here does not override evidence elsewhere.",
+  "properties": {
+    "approvalPolicy": {
+      "description": "Referral reward approval policy from requireManualRewardApproval, not affiliate commission approval or an individual reward state.",
+      "enum": [
+        "manual",
+        "automatic",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "automaticFulfillmentMarking": {
+      "description": "The autoFulfillRewards setting, when returned by an options read. Null means unknown; this controls marking, not delivery.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "basis": {
+      "enum": [
+        "this_response_only"
+      ],
+      "type": "string"
+    },
+    "conclusion": {
+      "type": "string"
+    },
+    "deliveryStatus": {
+      "enum": [
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "integrationConnection": {
+      "enum": [
+        "not_established"
+      ],
+      "type": "string"
+    },
+    "nextStep": {
+      "type": "string"
+    },
+    "programReferralTrigger": {
+      "enum": [
+        "not_established"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.12.2Aug 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations readOnlyHint=true, idempotentHint=true, destructiveHint=false already tell the agent this is a safe read operation. The description adds behavioral nuance by noting the `autoFulfillRewards: false` does NOT prove rewards went undelivered (a corrective against misinterpretation), and clarifies that passing `campaignId` is optional with a default. This goes beyond the annotations without contradicting them.

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 packs essential details into a few sentences: what is fetched, the return shape, the autoFulfillRewards caveat, and the targeting default. It is front-loaded with the purpose, and every sentence adds value. No fluff or redundancy.

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

Completeness4/5

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

Given the low complexity (1 optional param), high schema coverage, and presence of an output schema, the description is quite complete. It mentions return shape ('same shape you send back on update') and cautions against misinterpreting a field. Missing only explicit indication of which specific fields exist, but the output schema covers that. Strong for the tool's complexity.

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

Parameters3/5

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

Schema description coverage is 100% (the description for campaignId explains the default and how to get the id from create_campaign). The description itself does not add much beyond the schema, but it reinforces the default behavior architecturally which is already in the schema. Baseline 3 is appropriate.

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?

The description clearly states 'Fetch the Options tab configuration' and lists what is included (referral triggers, anti-fraud lists, notifications, etc.), which is specific and distinguishes it from related tools like update_campaign_options. However, it doesn't explicitly contrast with siblings that might also fetch campaign configuration (e.g., get_campaign_design, get_campaign_emails), though the listing of scope is enough to infer differentiation.

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 provides context on when to use it (fetch options) and explains the `campaignId` targeting behavior including the default to GROWSURF_CAMPAIGN_IDepth. It does not explicitly exclude alternatives or say when NOT to use it, but it is clear enough for an agent to know it's the right call for reading options. The caveat about autoFulfillRewards is more of a semantic clarification than usage guidance.

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

Deploy Server