campaignstack

campaignstack_update_workspace_compliance

Turn the GDPR Article 14 lawful-basis notice on or off for a workspace (lawfulBasisNoticeEnabled). Call this only when the user explicitly asks to turn the notice on or off. When on, one fixed sentence and a link are appended to the first LinkedIn message or email each person receives; the text is not editable here. Pass null to reset to the default (off). Owner/admin only for user API keys.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`workspaceId`	No	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.
`lawfulBasisNoticeEnabled`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`notice`	No
`stored`	No
`resolved`	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": {
+    "error": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "notice": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "additionalProperties": true,
+              "properties": {
+                "text": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "text",
+                "url"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ok": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "resolved": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "additionalProperties": true,
+              "properties": {
+                "lawfulBasisNoticeEnabled": {
+                  "type": "boolean"
+                }
+              },
+              "required": [
+                "lawfulBasisNoticeEnabled"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "stored": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "additionalProperties": true,
+              "properties": {
+                "lawfulBasisNoticeEnabled": {
+                  "type": [
+                    "boolean",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "lawfulBasisNoticeEnabled"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 13, 2026

addedInput schema / properties / workspaceId / description

Added value: +"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."

AddedSep 10, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnly=false annotation, the description discloses concrete side effects: when enabled, a fixed sentence and link are appended to the first LinkedIn message or email each person receives. It also documents the null-reset behavior, the default state (off), and the auth restriction, all of which are genuinely useful and not present in the annotations.

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?

Four sentences, all information-dense and purposeful. The action is stated first, followed by when to call, the behavioral side effect, how to reset, and permission requirements. No filler or repetition of schema details.

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?

Given the tool's moderate complexity, the description covers the action, invocation trigger, side effects, default behavior, reset semantics, and permissions. The output schema already handles return-value documentation, and the workspaceId nuances are covered in the schema, so nothing essential is missing.

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 only 50%, with lawfulBasisNoticeEnabled lacking a description. The tool description compensates by explaining its on/off semantics, the null reset to default, and the fixed non-editable text behavior. It also reinforces the workspaceId concept by framing it as a workspace-level setting, adding value beyond the raw boolean type.

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 opens with a specific verb and resource: turning the GDPR Article 14 lawful-basis notice on or off for a workspace. It also names the relevant field (lawfulBasisNoticeEnabled), making the tool unmistakable and clearly distinct from siblings like get_workspace_compliance or update_workspace.

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 invocation condition: call only when the user explicitly asks to turn the notice on or off. It also adds a permission constraint (owner/admin only for user API keys) and implicitly warns against using it to edit notice text by stating the text is not editable here.

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?