Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Get Payout Destination

growsurf_get_participant_payout_destination
Read-onlyIdempotent

Retrieve a participant's payout-destination status across enabled PayPal, Venmo, or Wise providers, including active provider, confirmed email, recipient type, and repair reasons.

Instructions

Get a participant's payout-destination status (by GrowSurf participant ID or email) across every payout provider enabled for the program (PayPal, Venmo, or Wise). For each provider it reports the current status, the confirmed payout email, the legal recipient type, and — when a delivery bounced or a recipient was invalidated — the repair reason. activeProvider is the provider that currently gets paid, or null until the participant confirms one. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

NameRequiredDescriptionDefault
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
destinationsNoOne entry per enabled payout provider describing the participant's destination for it.
activeProviderNoThe payout provider currently selected, or `null` until the participant confirms one. Provider identifiers are open-ended; current examples include `PAYPAL`, `VENMO`, and `WISECOM`.
enabledProvidersNoPayout provider identifiers enabled for this program. Values are open-ended; current examples include `PAYPAL`, `VENMO`, and `WISECOM`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Changed2 schema fields changedv0.19.15
    • addedInput schema / properties / campaignId / minLength
      Added value: +1
    • addedInput schema / required
      Added value: +[
      +  "campaignId"
      +]
  3. 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."
  4. Changed3 schema fields changedv0.19.7
    • changedOutput schema / properties / activeProvider / description
      Previous value: -"The payout provider currently selected, or `null` until the participant confirms one. Provider identifiers are open-ended; current examples include `PAYPAL` and `WISECOM`."New value: +"The payout provider currently selected, or `null` until the participant confirms one. Provider identifiers are open-ended; current examples include `PAYPAL`, `VENMO`, and `WISECOM`."
    • changedOutput schema / properties / destinations / items / properties / provider / description
      Previous value: -"The payout provider identifier for this entry. Values are open-ended; current examples include `PAYPAL` and `WISECOM`."New value: +"The payout provider identifier for this entry. Values are open-ended; current examples include `PAYPAL`, `VENMO`, and `WISECOM`."
    • changedOutput schema / properties / enabledProviders / description
      Previous value: -"Payout provider identifiers enabled for this program. Values are open-ended; current examples include `PAYPAL` and `WISECOM`."New value: +"Payout provider identifiers enabled for this program. Values are open-ended; current examples include `PAYPAL`, `VENMO`, and `WISECOM`."
  5. First observedv0.12.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds that results span every enabled provider and explains the non-obvious `activeProvider` null state (unconfirmed participant). The mentions of `status`, confirmed payout email, legal recipient type, and repair reason add semantic context even though the output schema carries the concrete shape.

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?

Two dense sentences that front-load the purpose and then the returned semantics; every clause earns its place. Slight repetition of the campaignId fallback already present in the schema is the only waste.

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?

With an output schema present and annotations covering the safety profile, the description only needs to orient the agent on identity inputs, targeting, and the meaning of key fields, which it does. Nothing essential for calling it correctly 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 33%, leaving participantId and participantEmail undescribed in the schema; the description partially compensates by stating that lookup is by participant ID or email. The campaignId fallback sentence merely restates the schema's own description, and nothing is said about precedence when both participant identifiers are supplied.

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 ('Get a participant's payout-destination status') and scopes it to all payout providers enabled for the program, which is far more than a restatement of the name. It does not explicitly differentiate itself from the sibling 'growsurf_request_participant_payout_destination_confirmation', so an agent must infer that one reads and the other initiates.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no conditions for choosing this over the request-confirmation sibling, and no statement of prerequisites. The only routing-like sentence ('Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID') is parameter behavior rather than usage context.

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