Skip to main content
Glama
Sign In
GrowSurf MCP Server

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Bulk Move Participants

growsurf_bulk_move_participants
DestructiveIdempotent

Moves up to 200 GrowSurf participants by ID or email to a specified group or Default in one atomic bulk request, returning per-row statuses.

Instructions

Move participants in your GrowSurf program to a group, or to Default with groupId: null. Each entry in participants is a GrowSurf participant ID or an email address (mixed lists are allowed), up to 200 entries per request. All found participants move together: if the move fails, no one moves. A move is a manual placement, so the groups' email and domain rules do not override it later. A move applies to new referrals only; rewards already earned keep their amounts. Returns a summary (total, groupId, movedCount, notFoundCount, duplicateCount, errorCount) plus per-row results in request order, each with status MOVED, NOT_FOUND, DUPLICATE, or ERROR. 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": {
      "participants": "<participants>",
      "groupId": "<groupId>",
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_bulk_move_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesThe group to move them to (`grp_…`), or `null` for Default. Required.
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.
participantsYesGrowSurf participant IDs and/or email addresses to move (1-200 entries; mixed lists allowed).

Output Schema

NameRequiredDescriptionDefault
resultsNoOne entry per submitted identifier, in request order.
summaryNoCounts across all submitted entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.32

TDQS

A4/5.0
Behavior5/5

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

Goes well past the annotations (destructiveHint=true, idempotentHint=true) by disclosing atomicity ('All found participants move together: if the move fails, no one moves'), that placement is manual and immune to later group rule evaluation, and that rewards already earned are preserved at their current amounts. Those are exactly the consequences an agent needs before firing a destructive bulk operation, and none are derivable from the structured fields.

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?

Front-loaded with the action and destination, then escalating detail: input format, atomicity, rule semantics, return shape, target resolution. Every sentence carries weight except the return-value enumeration, which partly duplicates the existing output schema and could be trimmed.

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 3-required-param destructive bulk tool with an output schema and full schema coverage, the description covers the remaining gaps: atomicity, target resolution order, rule-override semantics, and the per-row status vocabulary. An agent could call this correctly without opening any other resource.

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%, so the schema already documents groupId (null for Default), campaignId (env fallback), and participants (1-200 mixed IDs/emails). The description restates these facts (mixed lists allowed, 200 max, null for Default) rather than adding new meaning such as ID prefixes or duplicate handling in the target group. Baseline 3 applies when the schema carries the load.

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?

Opens with a specific verb+resource+scope: 'Move participants in your GrowSurf program to a group, or to Default with groupId: null.' The action and its two possible destinations are unambiguous. It stops short of naming a sibling (e.g., growsurf_bulk_delete_participants or growsurf_add_participant) to reinforce the boundary, so differentiation is inferred from the name rather than stated.

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?

Gives strong context on targeting ('Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID') and a key pre-condition about rule interaction ('A move is a manual placement, so the groups' email and domain rules do not override it later'). However, it never states when to prefer this over add_participant or bulk_delete_participants, nor any explicit when-not-to-use condition, leaving the routing decision to inference.

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