Skip to main content
Glama
growsurf

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Request Payout Destination Confirmation

growsurf_request_participant_payout_destination_confirmation
Destructive

Ask a participant to confirm their payout destination for an enabled provider by ID or email; sends a one-time link only they can open to verify.

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

TableJSON Schema
NameRequiredDescriptionDefault
providerYesThe payout provider the participant should confirm a destination for.
campaignIdNoTarget program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server.
participantIdNo
participantEmailNo

Output Schema

TableJSON 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.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."
  2. 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`."
  3. First observedv0.12.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: the message is a one-time link, only the participant can open and confirm it, and the call merely triggers the send rather than completing confirmation. This meaningfully clarifies the side-effect semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Content is front-loaded: what it does, how it works, the caveat, the return shape, and campaign targeting. Every sentence carries distinct information and nothing is padded.

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?

Covers the delivery mechanism, the prerequisite (provider enabled), the targeting/default behavior for campaignId, and even the return fields. With an output schema present the return detail is optional but consistent, and no information an agent needs to invoke it correctly 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 50%, with participantId and participantEmail undocumented in the schema; the description compensates by stating selection is 'by GrowSurf participant ID or email'. The provider parameter is enum-documented in the schema, and the description reinforces that the provider must be enabled. It adds useful meaning over the schema without fully detailing formats.

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?

States a specific verb and resource: asks a participant to confirm a payout destination. It also clarifies the exact mechanism (sends a one-time confirmation link) and that it only triggers the message rather than performing the confirmation, which distinguishes it from a plain read of destinations. It stops short of naming the sibling growsurf_get_participant_payout_destination, so sibling differentiation relies on the reader.

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?

Gives clear context for use (participant must confirm a payout destination for a given provider) and a real prerequisite (the provider must be enabled for the program). It does not state when NOT to use it or name an alternative sibling, so it lacks explicit 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