GrowSurf

Update Campaign Group

growsurf_update_campaign_group

DestructiveIdempotent

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. Group names must be unique in the program (case is ignored), and "Default" is reserved. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

Name	Required	Description
`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	Replaces the group's whole rule list. Up to 500.
`groupId`	Yes	The group ID (`grp_…`).
`campaignId`	Yes	Target program id for this call: the `id` returned by `growsurf_list_campaigns`, not the program name or a share URL. 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.

Changed2 schema fields changedNov 13, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "name"
+    ]
+  },
+  {
+    "required": [
+      "order"
+    ]
+  },
+  {
+    "required": [
+      "rules"
+    ]
+  }
+]

changedInput schema / properties / campaignId / description

Previous 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."New value: +"Target program id for this call: the `id` returned by `growsurf_list_campaigns`, not the program name or a share URL. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."

AddedNov 12, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, yet the description goes further: "Sending `rules` replaces the whole list," an added PARTICIPANT rule moves them in now, a removed one moves them back to Default, and email/domain changes move no one. Those are exactly the side effects an agent needs before a destructive write.

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-loaded with the operation set, then consequences, then the cross-tool pointer, then constraints, then targeting. Every sentence carries a distinct fact; nothing is restated from the schema verbatim.

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?

For a destructive, idempotent mutation with 5 parameters, the description covers side effects, replacement semantics, uniqueness/reserved-name rules, and campaign targeting. An output schema exists, so return values need no explanation here.

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 would be 3, but the description adds meaning beyond it: whole-list replacement semantics for `rules`, the fact that email/domain rules only affect future signups and approvals, and the campaignId-vs-GROWSURF_CAMPAIGN_ID targeting rule. The uniqueness and reserved "Default" constraints on `name` are also surfaced.

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?

Opens with a specific verb set plus resource: "Rename, reorder, or change the rules of a group on your GrowSurf program." It also explicitly excludes reward changes and routes them to growsurf_update_campaign_reward, so an agent can separate it from the closest sibling 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?

Gives clear conditions for the three mutation modes and names the alternative tool for the adjacent-but-different task (rewards). It does not explicitly address create-vs-update or delete, but the operation set is unambiguous for an update tool.

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.