GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Program

growsurf_get_campaign

Read-onlyIdempotent

Fetch your GrowSurf campaign (program) details via REST. Embedded reward settings do not establish that an individual reward was earned, approved, or delivered. Earned reward records belong to the individual participant.

Instructions

Input Schema

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

Output Schema

Name	Required	Description
`id`	No	The program's unique id.
`name`	No	The program name (internal only, never shown to participants).
`type`	No	The program type.
`status`	No	The program status.
`rewards`	No	The program's reward configs (`CampaignReward`). Item shape is documented on the `growsurf_list_campaign_rewards` tool.
`currencyISO`	No	The program currency as an ISO 4217 code (e.g. `USD`).
`inviteCount`	No	Total invites sent by participants.
`winnerCount`	No	Participants with at least one approved reward.
`referralCount`	No	Total referrals.
`rewardEvidence`	No	What this response establishes about rewards. Combine with other reads; unknown here does not override evidence elsewhere.
`impressionCount`	No	Total referral-link views across participants.
`participantCount`	No	Total participants.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.19.23Oct 22, 2026

changedOutput schema / properties / status / enum

Previous value: -[
-  "DRAFT",
-  "IN_PROGRESS",
-  "COMPLETE",
-  "DELETED"
-]New value: +[
+  "DRAFT",
+  "PENDING",
+  "IN_PROGRESS",
+  "COMPLETE",
+  "CANCELLED",
+  "DELETED"
+]

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

Changed1 schema field changedv0.14.0Sep 10, 2026

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

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so safety is covered. The description adds genuinely non-obvious context: that embedded reward settings are configuration, not evidence a reward was earned/approved/delivered, and that earned records belong to the participant. That is real domain semantics beyond the structured fields.

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?

The core action is front-loaded in the first clause, and the three sentences are tight. The reward-settings disclaimer is somewhat tangential to fetching a campaign but earns its place by preventing a mistaken inference about earned rewards.

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

Completeness5/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 not be described, and annotations cover the safety profile. The description supplies the campaignId resolution rule and the reward-semantics caveat, which is sufficient for an agent to call this single-parameter read tool correctly.

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% and the sole parameter is already documented, including the GROWSURF_CAMPAIGN_ID default. The description's mention of the same fallback and env var duplicates the schema rather than adding format or constraint detail. Baseline 3 applies.

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 ('Fetch') and resource ('GrowSurf campaign (program) details') with the transport noted (REST). An agent can tell this returns the campaign entity itself. It does not, however, differentiate from sibling getters like get_campaign_options, get_campaign_design, or get_campaign_analytics, so the boundary is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to choose this over the many other campaign-scoped getters (options, design, installation, emails, analytics, list_campaigns). The only usage-like guidance is the parameter targeting rule, which is a resolution mechanic rather than when-to-use guidance.

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

Deploy Server