GrowSurf

Get Integration Connect Link

growsurf_get_integration_connect_link

Read-onlyIdempotent

Return a dashboard link to an integration's connect panel in the GrowSurf Program Editor (Options > Integrations). Connecting Stripe, PayPal, Wise, or another account requires the user to complete the dashboard flow; the API cannot connect an account on their behalf. integration accepts supported keys, including camelCase keys such as constantContact and helpScout. The result reports whether the integration is connected, enabled, or autoDisabled. If the program check cannot run, programVerified is false and the result still includes a production dashboard link. Tango Card, Tremendous, Bask Health, CareValidate, MD Integrations, Lithos, and Telegra apply only to referral programs. Wise applies only to affiliate programs. Targets campaignId if supplied, 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": {
      "integration": "<integration>"
    },
    "name": "growsurf_get_integration_connect_link"
  }
}

Input Schema

Name	Required	Description	Default
`campaignId`	No	Target program for the link. Defaults to GROWSURF_CAMPAIGN_ID.
`integration`	Yes	The integration to connect. Must exactly match one of the supported keys (for example `wisecom`; some are camelCase, e.g. `constantContact`, `campaignMonitor`, `helpScout`, `pabblyConnect`, `baskHealth`).

Output Schema

Name	Required	Description
`url`	No	Dashboard link that opens the integration's connect panel.
`note`	No	Instructions to relay to the user.
`label`	No	Human-readable integration name.
`enabled`	No	Whether the integration is switched on and currently working. Present only when `programVerified` is `true`.
`category`	No	The integration's category.
`connected`	No	Whether the program has stored credentials for this integration. Present only when `programVerified` is `true`.
`integration`	No	The integration key that was requested.
`autoDisabled`	No	Whether GrowSurf switched the integration off after repeated delivery failures. Present only when `programVerified` is `true`.
`referralOnly`	No	`true` when the integration applies to referral programs only.
`affiliateOnly`	No	`true` when the integration applies to affiliate programs only.
`programVerified`	No	`true` when the program's live integration list was read, so the program id is confirmed and the three state fields below are present and current. `false` when that read was unavailable, for example without an API key or `program:read`: the link still works but points at the production dashboard, and the state fields are omitted because the state is unknown. Never treat an absent state field as `false`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / integration / enum

Previous value: -[
-  "stripe",
-  "chargebee",
-  "recurly",
-  "paypal",
-  "wisecom",
-  "tangoCard",
-  "tremendous",
-  "hubspot",
-  "salesforce",
-  "marketo",
-  "mailchimp",
-  "activecampaign",
-  "braze",
-  "bentonow",
-  "mailerlite",
-  "resenddotcom",
-  "loopsdotso",
-  "convertkit",
-  "constantContact",
-  "campaignMonitor",
-  "aweber",
-  "klaviyo",
-  "mailjet",
-  "sendgrid",
-  "sendinblue",
-  "emailoctopus",
-  "customerio",
-  "getresponse",
-  "drip",
-  "googleanalytics",
-  "segmentanalytics",
-  "posthoganalytics",
-  "mixpanelanalytics",
-  "pendo",
-  "fullstory",
-  "heapanalytics",
-  "amplitude",
-  "googleads",
-  "metaads",
-  "linkedinads",
-  "twitterads",
-  "slack",
-  "intercom",
-  "helpScout",
-  "zapier",
-  "integromat",
-  "pabblyConnect",
-  "webhook",
-  "baskHealth",
-  "tangocard"
-]New value: +[
+  "stripe",
+  "chargebee",
+  "recurly",
+  "paypal",
+  "wisecom",
+  "tangoCard",
+  "tremendous",
+  "hubspot",
+  "salesforce",
+  "marketo",
+  "mailchimp",
+  "activecampaign",
+  "braze",
+  "bentonow",
+  "mailerlite",
+  "resenddotcom",
+  "loopsdotso",
+  "convertkit",
+  "constantContact",
+  "campaignMonitor",
+  "aweber",
+  "klaviyo",
+  "mailjet",
+  "sendgrid",
+  "sendinblue",
+  "emailoctopus",
+  "customerio",
+  "getresponse",
+  "drip",
+  "googleanalytics",
+  "segmentanalytics",
+  "posthoganalytics",
+  "mixpanelanalytics",
+  "pendo",
+  "fullstory",
+  "heapanalytics",
+  "amplitude",
+  "googleads",
+  "metaads",
+  "linkedinads",
+  "twitterads",
+  "slack",
+  "intercom",
+  "helpScout",
+  "zapier",
+  "integromat",
+  "pabblyConnect",
+  "webhook",
+  "baskHealth",
+  "carevalidate",
+  "mdIntegrations",
+  "lithos",
+  "telegra",
+  "tangocard"
+]

First observedOct 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the returned status fields (connected, enabled, autoDisabled), the programVerified=false fallback that still yields a production dashboard link, and program-type applicability rules. This is unusually rich behavioral context for a read tool.

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 core purpose and the user-must-do-it constraint, with secondary details (status fields, program-type rules, campaign targeting) after. Some integration enumeration is wordy but each clause carries functional 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?

An output schema exists, yet the description still usefully summarizes return states and the fallback case, and covers program-type applicability and campaign targeting. Nothing an agent needs to choose and call this tool 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 100% and already documents both parameters, including the enum and the GROWSURF_CAMPAIGN_ID fallback. The description restates the camelCase key caveat with examples (constantContact, helpScout) but adds no syntax or format detail beyond the schema, so 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?

States a specific verb and resource: it returns a dashboard link to an integration's connect panel in the Program Editor, with the exact UI path (Options > Integrations). This clearly separates it from siblings like list_integrations or integration_guide.

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?

Explicitly explains the when-not: connecting Stripe, PayPal, Wise, etc. requires the user to complete the dashboard flow, and the API cannot connect on their behalf. It also gives program-type conditions (referral-only integrations, Wise affiliate-only) and campaignId defaulting, but it does not name sibling tools it supersedes.

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.