campaignstack

campaignstack_link_integration

Idempotent

Make an integration the user already connected (apollo, instantly, clay, hubspot) available in another of their workspaces, without asking for the API key again. Call this after campaignstack_create_workspace when campaignstack_list_integrations on the new workspace comes back empty and the user has the provider elsewhere. The key is copied server-side and never returned. No-op when the workspace already has that provider. Refuses when the user has no connected integration of that provider anywhere; connect one first with campaignstack_connect_apollo, campaignstack_connect_instantly or campaignstack_connect_hubspot.

Input Schema

TableJSON Schema

Name	Required	Description
`provider`	Yes	Which integration to make available.
`workspaceId`	Yes	Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach. The workspace that should get the integration.
`fromWorkspaceId`	No	Only when the user has this provider connected in several workspaces: which one to copy from.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`provider`	No
`workspaceId`	No
`alreadyLinked`	No
`integrationId`	No
`sourceWorkspaceId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "alreadyLinked": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "integrationId": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "provider": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "sourceWorkspaceId": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "workspaceId": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds meaningful behavior beyond the idempotentHint annotation: the key is copied server-side and never returned, the operation is a no-op when the provider already exists in the target workspace, and it refuses when no connected integration exists anywhere. These are exactly the side effects and preconditions an agent needs to know.

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?

The description is dense but every sentence earns its place: purpose, trigger condition, behavioral guarantees, and failure handling. The most important purpose is front-loaded, and there is no fluff or repetition of schema content.

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 tool with this complexity, the description covers what it does, when to call it, prerequisites, no-op behavior, refusal behavior, and security-relevant detail about the API key. The output schema exists, so return-value documentation is not required from the description, and nothing important is left ambiguous.

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 description coverage is 100% and the schema already explains provider, workspaceId, including the csu_/cs_ key distinction, and fromWorkspaceId. The description adds operational context like 'without asking for the API key again' but does not provide parameter-level details beyond what the schema already covers.

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 states a specific verb and resource: making an already-connected integration available in another workspace without re-requesting the API key. It also names the supported providers and clearly distinguishes this from connecting a new integration or listing integrations.

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

Usage Guidelines5/5

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

It gives an explicit trigger condition: call after campaignstack_create_workspace when campaignstack_list_integrations on the new workspace is empty and the provider exists elsewhere. It also specifies no-op and refusal behavior, and routes the user to connect tools when no integration exists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All campaignstack 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.

Resources

Need Help?