Skip to main content
Glama
Sign In
GrowSurf MCP Server

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Campaign Groups

growsurf_list_campaign_groups
Read-onlyIdempotent

List a GrowSurf program's participant groups in display order to see which reward lists replace the Default rewards for members' new referrals.

Instructions

List your GrowSurf program's groups in display order. Groups give some participants a different reward list. Each participant is in one group, and groupId: null is Default, which holds the program's standard rewards and is not in this list. A group's rewards replace Default's whole reward list for its members' new referrals. Leaderboard rewards stay program-wide. 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": {
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_list_campaign_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
groupsNoThe program's groups in display order. Default is not listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.32

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond them: results are in display order, the Default group is deliberately never returned (groupId: null), and a group's rewards replace Default's entire reward list for new referrals while leaderboard rewards stay program-wide. That last point is genuinely useful semantics an agent could not derive 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?

Four sentences, front-loaded with the action and ordering, then the domain model, then the targeting rule. Every sentence carries information, though the reward-replacement explanation is slightly dense and could be tightened without loss. No filler or repetition of the title.

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?

A read-only list tool with a single fully documented parameter, full annotation coverage, and an output schema (so return values need no explanation). The description explains the domain model an agent needs to interpret the results, most importantly that Default is absent from the list, which prevents a common misinterpretation.

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 single parameter is fully documented, including the GROWSURF_CAMPAIGN_ID fallback, so the baseline is 3. The description's restatement of the targeting rule adds no meaning beyond the schema, and there are no details about display-order direction or pagination limits.

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?

The first sentence gives a specific verb and resource ('List your GrowSurf program's groups') plus the ordering contract ('in display order'), which is more than a restatement of the title. It stops short of naming the sibling that creates or deletes groups, so the agent must infer that this tool is the read counterpart to growsurf_create_campaign_group/growsurf_delete_campaign_group.

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

Usage Guidelines3/5

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

Usage is implied through domain framing: groups give some participants a different reward list, and Default is excluded from this list. There is no explicit 'use this when...' or 'use X instead' routing, and the campaignId resolution rule is stated but not framed as a decision criterion. Adequate context, no exclusions.

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