Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Request Payout Destination Confirmation

growsurf_request_participant_payout_destination_confirmation
Destructive

Sends a participant a one-time link to confirm their payout destination for PayPal, Venmo, or Wisecom, triggering confirmation for the selected provider and campaign.

Instructions

Ask a participant to confirm their payout destination for a provider (by GrowSurf participant ID or email). Sends them a one-time confirmation link for the chosen provider; only the participant can open the link and confirm — this just triggers the message, and the provider must be enabled for the program. Returns { status, provider, providerDisplayName, expiresAt }. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

NameRequiredDescriptionDefault
providerYesThe payout provider the participant should confirm a destination for: `PAYPAL`, `VENMO`, or `WISECOM`. `VENMO` is available only when connected PayPal Payouts and payout-email confirmation are enabled in a USD program. Venmo recipients must be in the United States.
campaignIdYesTarget 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.
participantIdNo
participantEmailNo

Output Schema

NameRequiredDescriptionDefault
statusNoConfirms the message was requested (`CONFIRMATION_REQUESTED`).
providerNoThe payout provider identifier the participant was asked to confirm. Values are open-ended; current examples include `PAYPAL`, `VENMO`, and `WISECOM`.
expiresAtNoWhen the confirmation link expires, as a Unix timestamp in milliseconds.
providerDisplayNameNoThe customer-facing provider name (e.g. "PayPal", "Wise").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.34
    • changedInput schema / properties / provider / description
      Previous value: -"The payout provider the participant should confirm a destination for: `PAYPAL`, `VENMO`, or `WISECOM`. Venmo recipients must be in the United States."New value: +"The payout provider the participant should confirm a destination for: `PAYPAL`, `VENMO`, or `WISECOM`. `VENMO` is available only when connected PayPal Payouts and payout-email confirmation are enabled in a USD program. Venmo recipients must be in the United States."
  2. Changed1 schema field changedv0.19.33
    • 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."
  3. Changed1 schema field changedv0.19.27
    • changedInput schema / properties / provider / description
      Previous value: -"The payout provider the participant should confirm a destination for."New value: +"The payout provider the participant should confirm a destination for: `PAYPAL`, `VENMO`, or `WISECOM`. Venmo recipients must be in the United States."
  4. Changed2 schema fields changedv0.19.15
    • addedInput schema / properties / campaignId / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
      -  "provider"
      -]New value: +[
      +  "provider",
      +  "campaignId"
      +]
  5. Changed1 schema field changedv0.19.9
    • changedInput schema / properties / campaignId / description
      Previous value: -"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Pass the `id` returned by growsurf_create_campaign to configure or operate a program you just created, without restarting the server."New 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."
  6. Changed2 schema fields changedv0.19.7
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "PAYPAL",
      -  "WISECOM"
      -]New value: +[
      +  "PAYPAL",
      +  "VENMO",
      +  "WISECOM"
      +]
    • changedOutput schema / properties / provider / description
      Previous value: -"The payout provider identifier the participant was asked to confirm. Values are open-ended; current examples include `PAYPAL` and `WISECOM`."New value: +"The payout provider identifier the participant was asked to confirm. Values are open-ended; current examples include `PAYPAL`, `VENMO`, and `WISECOM`."
  7. First observedv0.12.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a mutating, non-idempotent, open-world operation; the description adds real context beyond them: a one-time link is sent, only the participant can open it, and the call does not itself change the destination. It omits whether repeated calls resend the message and what happens when the provider is not enabled.

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?

Three sentences, front-loaded with the action and the participant identifier, then prerequisites and return shape. Dense but every clause carries information; the parenthetical about return fields is the least necessary given an output schema exists.

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 four-parameter mutation with an output schema, the description covers identification method, provider constraints, campaign targeting, prerequisites, and the fact that it only sends a message. An agent has enough to call it correctly without reading further.

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 only 50% (participantId and participantEmail are bare), and the description compensates by explaining the ID-or-email choice that the anyOf encodes. It also clarifies campaignId resolution, though it says the value may fall back to GROWSURF_CAMPAIGN_ID while the schema lists campaignId as required — a small inconsistency.

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 description opens with a specific verb and resource: 'Ask a participant to confirm their payout destination for a provider,' plus the two ways to identify the participant. It implicitly distinguishes itself from the read-side sibling by stating 'this just triggers the message,' though it never names an alternative tool.

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 gives a clear use context (a participant needs to confirm a payout destination) and prerequisite gating ('the provider must be enabled for the program'). It does not explicitly say when not to use it or name the sibling that retrieves an existing destination instead.

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