Skip to main content
Glama
Sign In
GrowSurf MCP Server

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Campaign Group

growsurf_update_campaign_group
DestructiveIdempotent

Rename, reorder, or replace the rules of a GrowSurf campaign group to control which participants, emails, or domains belong to it.

Instructions

Rename, reorder, or change the rules of a group on your GrowSurf program. Sending rules replaces the whole list. An added PARTICIPANT rule moves that participant in now; a removed one moves them back to Default if they are still in this group. Email and domain rule changes move no one. To change the group's rewards, use growsurf_update_campaign_reward. 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": {
      "groupId": "<groupId>",
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_update_campaign_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe group name (internal only, never shown to participants).
orderNoThe group's position in the program's group list.
rulesNoReplaces the group's whole rule list. Up to 500.
groupIdYesThe group ID (`grp_…`).
campaignIdYesTarget 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

NameRequiredDescriptionDefault
idNoThe group ID (`grp_…`).
nameNoThe group name (internal only, never shown to participants).
orderNoThe group's position in the program's group list.
rulesNoThe rules that place participants in this group.
createdAtNoWhen the group was created, in Unix milliseconds.
updatedAtNoWhen the group was last changed, in Unix milliseconds.
signupCodeNoThe 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.

  1. Addedv0.19.32

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive=true, idempotent=true): it warns that sending `rules` replaces the entire list, explains that an added PARTICIPANT rule moves the participant immediately, that a removed rule returns them to Default only if still in the group, and that EMAIL/DOMAIN changes move no one. This is exactly the side-effect detail an agent needs before a destructive mutation.

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?

Front-loads the action, then the destructive `rules` warning, then per-type effects, then the sibling redirect, then targeting. Every sentence carries distinct information; nothing is redundant with the title.

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 no explanation, and annotations cover the safety profile. The description still supplies the destructive replace behavior, rule-type side effects, and campaign targeting, leaving no gap an agent would need before calling this mutation.

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 coverage is 100%, so baseline is 3, but the description adds meaning beyond it: the replace-not-merge semantics of `rules` and the per-rule-type migration behavior, plus the campaignId fallback to GROWSURF_CAMPAIGN_ID. It adds real interpretation value on top of an already documented schema.

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?

States specific verbs (rename, reorder, change rules) against a specific resource (a campaign group on the GrowSurf program). It also delineates scope from the reward-editing sibling by name, so an agent can distinguish it without opening either 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?

Explicitly routes reward changes to `growsurf_update_campaign_reward`, which is a real alternative among the siblings. It does not cover when to prefer create/delete group or what preconditions exist, but the key adjacent-tool exclusion is present.

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

Deploy Server

Other Tools