Skip to main content
Glama

campaignstack

by io.campaignstack
OverviewDiscussionsAdmin

campaignstack_get_workspace_memories

Read-onlyIdempotent

List workspace memories: active notes already used in prompts first, then candidate notes awaiting confirmation, each newest first. Each item carries status, observations (a candidate goes live at 3, from three different leads), direction (include: asks drafts to contain something; avoid: asks them to leave it out) and source (agent, user, user_edit for app edits, or mcp_edit for MCP edits). Page with pagination.nextCursor while pagination.hasMore is true.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, default 50, at most 100.
cursorNopagination.nextCursor from the previous page.
categoryNo
workspaceIdNoWorkspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.

Output Schema

NameRequiredDescriptionDefault
dataNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "pagination.nextCursor from the previous page.",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Page size, default 50, at most 100.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedOutput schema / properties / data / anyOf
      Previous value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "category": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "content": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "createdAt": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "leadId": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "source": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "title": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "category": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "content": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "createdAt": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "direction": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "leadId": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "observations": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "source": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "title": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / workspaceId / description
      Previous 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."New value: +"Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too."
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real domain behavior: the promotion rule ('a candidate goes live at 3, from three different leads'), what 'direction' include/avoid means for drafts, and the source taxonomy. It stops short of stating auth or scale limits, but the domain semantics are substantive.

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?

Two sentences, both dense with information and no filler: the first states scope and ordering, the second decodes the returned fields and pagination. Information is front-loaded with the listing semantics ahead of field-level detail.

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?

With an output schema present, the description needn't explain return shape, yet it helpfully glosses the key item fields and the pagination contract. What's missing is whether the category filter narrows memory type and any cue about when an agent should reach for this list.

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

Parameters4/5

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

Schema coverage is 75% and workspaceId is documented thoroughly in-schema, so the baseline is 3; the description earns an extra point by explaining the cursor loop concretely ('page with pagination.nextCursor while pagination.hasMore is true'), adding a termination condition the schema does not. The gap is that the category enum (rule/voice/audience/lesson/other) is never explained in either the schema or the description.

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?

Opens with a specific verb+resource ('List workspace memories') and immediately specifies the scope composition: active notes first, then candidates, each newest first. An agent can distinguish this read/list tool from siblings like campaignstack_edit_workspace_memory and campaignstack_delete_workspace_memory without opening any schema.

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

Usage Guidelines3/5

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

The description is about what the tool returns, not when to call it — there is no guidance such as 'call this before drafting to learn workspace preferences' and no explicit statement that mutations belong to campaignstack_edit_workspace_memory. Usage is only implied by 'List' versus the edit/delete siblings.

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

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