campaignstack

campaignstack_link_account_to_workspace

Idempotent

Make a LinkedIn or Google account the user already connected available in another of their workspaces, so that workspace can send from it. Call this after campaignstack_create_workspace when the user wants the new workspace to run on an account they already use elsewhere; read the accountId from campaignstack_list_accounts on a workspace that has it. The first LinkedIn account linked becomes the workspace's default sender. Nothing is sent and nothing is re-authenticated. The account must be the user's own and they must belong to the target workspace. Free accounts have an identity cap per workspace; the error says so when it bites. To connect a NEW account use campaignstack_request_connect_link.

Input Schema

TableJSON Schema

Name	Required	Description
`platform`	Yes	Which kind of account.
`accountId`	Yes
`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 the account should become available in.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`email`	No
`linked`	No
`platform`	No
`accountId`	No
`workspaceId`	No
`alreadyLinked`	No
`isWorkspaceDefault`	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": {
+    "accountId": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "alreadyLinked": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "email": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "isWorkspaceDefault": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "linked": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "platform": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "workspaceId": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 18, 2026

TDQS

A5/5.0

Behavior5/5

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

The description adds valuable behavior beyond annotations: 'Nothing is sent and nothing is re-authenticated', the first LinkedIn account becomes the default sender, and free accounts have an identity cap per workspace. These details are not present in the annotations and meaningfully shape agent expectations.

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 longer than average, but every sentence carries operational value: main action, when to call, where to get the ID, default sender behavior, side-effect guarantees, ownership prerequisites, failure mode, and alternative tool. It is front-loaded with the core purpose.

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 state-changing linking operation with three parameters, this description covers prerequisites, data provenance, side-effect boundaries, an ordering constraint, a failure mode, and the alternative path. An output schema exists, so return-value documentation is not required in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, leaving accountId undocumented, but the description compensates by saying to read accountId from campaignstack_list_accounts. It also reinforces the platform enum and clarifies that workspaceId is the target workspace, while the schema already covers user-key versus workspace-key behavior.

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 action: making an already-connected LinkedIn or Google account available in another workspace so that workspace can send from it. It clearly distinguishes itself from campaignstack_request_connect_link, which is for connecting a NEW account.

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 explicit when-to-use guidance: after campaignstack_create_workspace, when the user wants a new workspace to use an account already connected elsewhere. It also tells how to obtain the accountId via campaignstack_list_accounts and explicitly names the alternative for new accounts.

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?