Skip to main content
Glama
Sign In
GrowSurf MCP Server

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Campaign Group

growsurf_delete_campaign_group
DestructiveIdempotent

Delete a GrowSurf campaign group, moving its members to Default and removing its Campaign Rewards while preserving earned reward amounts for sending.

Instructions

Delete a group from your GrowSurf program. Its members move to Default, and its Campaign Rewards are removed from the program. Rewards already earned keep their amounts and can still be sent. Returns { id, success, movedToDefault }. 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_delete_campaign_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 deleted group ID.
successNoWhether the group was deleted.
movedToDefaultNoThe number of members moved to Default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.32

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, so the safety class is already known; the description goes further by spelling out the exact blast radius (members move to Default, Campaign Rewards are removed, earned rewards retain amounts and remain sendable). That is precisely the side-effect detail an agent needs before a destructive delete and it cannot be inferred from the annotations.

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?

Five short sentences, consequence-first ordering, zero filler. The return-shape sentence is mildly redundant given an output schema exists, but it is one clause and does not bloat the definition.

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 two-parameter destructive tool, the definition covers purpose, side effects, parameter targeting, and return shape; an output schema is present so return values are already covered. Nothing an agent needs in order to call this safely is missing.

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 the baseline is 3; the description adds a precedence statement ('Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID') that clarifies fallback resolution. This is largely duplicative of the schema's own default note, and it noticeably conflicts with campaignId being listed as required.

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 and resource ('Delete a group from your GrowSurf program'), which separates it cleanly from the create/update/list group siblings without needing their schemas. Scope is unambiguous and front-loaded.

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 clearly frames the destructive context and explains the campaignId/GROWSURF_CAMPAIGN_ID targeting choice, so an agent knows how to invoke it. It stops short of naming alternatives (e.g., update_campaign_group to rename rather than delete) or stating any when-not-to-use condition.

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