GrowSurf

Bulk Move Participants

growsurf_bulk_move_participants

DestructiveIdempotent

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

Name	Required	Description
`groupId`	Yes	The group to move them to (`grp_…`), or `null` for Default. Required.
`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.
`participants`	Yes	GrowSurf participant IDs and/or email addresses to move (1-200 entries; mixed lists allowed).

Output Schema

Name	Required	Description	Default
`results`	No	One entry per submitted identifier, in request order.
`summary`	No	Counts across all submitted entries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

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.2/5.0

Behavior5/5

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

Annotations only declare the safety profile (destructive, idempotent, open-world), while the description supplies the operationally important context: all-or-nothing atomicity ('if the move fails, no one moves'), that a manual placement is not later overridden by group email/domain rules, and that already-earned rewards keep their amounts. These are exactly the consequences an agent needs before firing 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense block with no filler sentences and the target/limit constraint front-loaded before the semantics and return details. It would scan faster as short bullets, but every sentence carries information.

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 bulk mutation, the definition covers target resolution (explicit `campaignId` vs GROWSURF_CAMPAIGN_ID), input limits, atomicity, side-effect semantics, and per-row outcome statuses. Nothing an agent needs to call it correctly or interpret partial failure is missing.

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 coverage is 100%, so `groupId` (null = Default), `campaignId` (env-var fallback), and `participants` (1-200, mixed lists) are already documented in structured fields. The description restates the 200-entry limit and mixed-list allowance without adding format, ordering, or validation meaning beyond the schema, so the baseline 3 applies.

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 precise verb and resource ('Move participants in your GrowSurf program to a group, or to Default with `groupId: null`'), and the scope (bulk, up to 200, mixed ID/email entries) is stated immediately. The verb 'move' cleanly separates it from the sibling set's delete, list, and add operations without needing to name them.

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 by the batch-move framing and the explicit null-target case, but there is no explicit when-to-use/when-not guidance relative to alternatives such as `growsurf_add_participant` or `growsurf_bulk_delete_participants`. The 'manual placement' and 'new referrals only' notes are behavioral rules rather than selection guidance, so an agent must infer the routing itself.

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.