campaignstack

campaignstack_whoami

Read-onlyIdempotent

Who this connection is and what it may do: the workspace it is bound to, the permissions the owner approved, and whether it is an API key or a connected app. Call it when a tool asks which workspace a call is for (a person in several workspaces names one; with only one, workspaceId defaults to it), and use campaignstack_explain_capabilities when the question is which tool to reach for rather than what is permitted. It reads nothing about leads or campaigns.

Input Schema

Name	Required	Description	Default
`include`	No

Output Schema

Name	Required	Description
`user`	No
`scopes`	No
`keyType`	No	workspace, user, oauth or stdio
`keyPrefix`	No
`workspaces`	No	Every workspace this person can reach, for the workspaceId argument. gettingStarted: setup rewards still open
`workspaceId`	No	Set only for a key bound to one workspace
`capabilities`	No	Each granted scope in plain words
`workspaceName`	No
`gettingStartedNote`	No
`notificationPreferences`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedOutput schema / properties / gettingStartedNote

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / workspaces / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "items": {
-          "additionalProperties": true,
-          "properties": {
-            "name": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "role": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "workspaceId": {
-              "type": [
-                "string",
-                "null"
-              ]
-            }
-          },
-          "type": "object"
-        },
-        "type": "array"
-      }
-    ],
-    "description": "Every workspace this person can reach, for the workspaceId argument"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {
+        "items": {
+          "additionalProperties": true,
+          "properties": {
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "role": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "workspaceId": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      }
+    ],
+    "description": "Every workspace this person can reach, for the workspaceId argument. gettingStarted: setup rewards still open"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / workspaces / description

Previous value: -"Every workspace this person can reach, for the workspaceId argument"New value: +"Every workspace this person can reach, for the workspaceId argument. gettingStarted: setup rewards still open"

Changed4 schema fields changedSep 26, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / include

Added value: +{
+  "additionalProperties": false,
+  "default": {},
+  "properties": {
+    "notificationPreferences": {
+      "default": false,
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / notificationPreferences

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {}
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "capabilities": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "items": {
+                "additionalProperties": true,
+                "properties": {
+                  "direction": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "means": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "note": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "scope": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          ],
+          "description": "Each granted scope in plain words"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Each granted scope in plain words"
+    },
+    "keyPrefix": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "keyType": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ],
+          "description": "workspace, user, oauth or stdio"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "workspace, user, oauth or stdio"
+    },
+    "scopes": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "user": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "additionalProperties": true,
+              "properties": {
+                "email": {
+                  "anyOf": [
+                    {
+                      "type": [
+                        "string",
+                        "null"
+                      ]
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "id": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "name": {
+                  "anyOf": [
+                    {
+                      "type": [
+                        "string",
+                        "null"
+                      ]
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                }
+              },
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "workspaceId": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ],
+          "description": "Set only for a key bound to one workspace"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Set only for a key bound to one workspace"
+    },
+    "workspaceName": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "workspaces": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "items": {
+                "additionalProperties": true,
+                "properties": {
+                  "name": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "role": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "workspaceId": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          ],
+          "description": "Every workspace this person can reach, for the workspaceId argument"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Every workspace this person can reach, for the workspaceId argument"
+    }
+  },
+  "type": "object"
+}

First observedSep 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value on top: the exact scope of what is disclosed (binding, approved permissions, credential type) and an explicit statement of what is not read (leads/campaigns), plus the workspaceId defaulting rule.

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 sentences, front-loaded with the identity/purpose clause before the routing guidance. Dense but essentially waste-free; the long parenthetical slightly reduces readability but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be described. The description covers identity, permissions, routing, and negative scope for a zero-required-param read tool; the only omission is any mention of the optional 'include' parameter.

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

Parameters2/5

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

Schema description coverage is 0% and the single optional parameter 'include' (nested, with notificationPreferences) is never mentioned in the description. There is only one optional param and its name is semi-intuitive, which keeps this above a 1, but the description does not compensate for the documentation gap.

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+resource: reports who the connection is (identity), which workspace it is bound to, which permissions the owner approved, and whether it is an API key or connected app. It also explicitly distinguishes itself from campaignstack_explain_capabilities, so an agent can route without opening either schema.

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?

Gives an explicit trigger ('call it when a tool asks which workspace a call is for'), a named alternative for the adjacent question ('use campaignstack_explain_capabilities when the question is which tool to reach for'), and a negative scope ('reads nothing about leads or campaigns'). When/when-not/alternative are all present.

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?