GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Campaign Group

growsurf_create_campaign_group

Create a participant group on a GrowSurf program to segment affiliates by email, company domain, or existing participant. Each new group copies your Default rewards so you can tailor them per group.

Instructions

Create a group on your GrowSurf program. GrowSurf copies each active Default reward into it, except Leaderboard rewards; change the copies with growsurf_update_campaign_reward. rules place participants: EMAIL matches an exact email, DOMAIN matches a company domain (public email domains are refused), and PARTICIPANT moves an existing participant in now. Each email and domain can be in one group only. Email and domain rules place new signups and affiliate approvals only. Confirm reward amounts with the person before you change the copies. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_create_campaign_group"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The group name (internal only, never shown to participants).
`rules`	No	The rules that place participants in this group. Up to 500.
`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 group ID (`grp_…`).
`name`	No	The group name (internal only, never shown to participants).
`order`	No	The group's position in the program's group list.
`rules`	No	The rules that place participants in this group.
`createdAt`	No	When the group was created, in Unix milliseconds.
`updatedAt`	No	When the group was last changed, in Unix milliseconds.
`signupCode`	No	The code for this group's signup link. A participant who signs up through the link joins this group.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.19.32Nov 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false, idempotentHint=false), the description discloses major side effects the agent could not infer: GrowSurf copies each active Default reward into the new group except Leaderboard rewards, and those copies must be changed separately. It also states hard constraints (each email and domain can belong to only one group; public email domains are refused) and timing semantics for rule types.

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?

Purpose is front-loaded in the first clause, and subsequent sentences cover side effects, rule semantics, exclusivity, and targeting with no filler. It is dense and packs several distinct topics into one block, which slightly hurts scannability but every sentence carries information.

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?

With an output schema present, return values need not be explained, and the annotations cover the safety profile; the description fills in the side effects, rule behavior, and targeting fallback that matter for correct invocation. It stops short of covering error/failure behavior (e.g., duplicate group names) for a non-idempotent creation call.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds constraints absent from the schema: public email domains are refused for DOMAIN rules, each email/domain may live in only one group, and DOMAIN also matches subdomains. The campaignId defaults are already documented in the schema, so that portion is repetition rather than added value.

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 specific verb+resource ("Create a group on your GrowSurf program") and immediately names the sibling that handles a related but different job (`growsurf_update_campaign_reward`) for adjusting the copied rewards. An agent can distinguish creating a group from updating rewards or deleting/updating groups without opening a schema.

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?

It gives real usage context: rules place participants, EMAIL/DOMAIN rules only affect new signups and affiliate approvals, while PARTICIPANT moves an existing participant in immediately. It also adds a policy instruction ("Confirm reward amounts with the person before you change the copies"). No explicit when-not-to-use or routing to `growsurf_update_campaign_group`/`growsurf_list_campaign_groups`, but the guidance is otherwise concrete.

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

Deploy Server