Skip to main content
Glama

campaignstack

by io.campaignstack
OverviewDiscussionsAdmin

campaignstack_list_agent_memories

Read-onlyIdempotent

List everything the agent memory system holds for this workspace, including notes still awaiting confirmation. A note the system only inferred from one of your edits (status "candidate") is not yet used in any prompt; a note asserted by an agent or applied by a person (status "active") already is. Call this when the user asks what the AI has learned, what notes are pending, or wants to review its memory. Apply a pending note with campaignstack_apply_agent_memory, or remove any note (pending or active) with campaignstack_delete_agent_memory. There is no edit tool: editing a pending note would let it skip the confirmation it is waiting for, so replace it by deleting the old one and letting the correction show up again, or by asserting a new one directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo
workspaceIdNoWorkspace 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "anyOf": [
+        {
+          "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"
+        }
+      ]
+    },
+    "pagination": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "additionalProperties": true,
+              "properties": {
+                "hasMore": {
+                  "type": [
+                    "boolean",
+                    "null"
+                  ]
+                },
+                "nextCursor": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "totalCount": {
+                  "description": "Total matching rows when known",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavior beyond that: it defines candidate vs active statuses, explains that candidate notes are not used in prompts, and discloses the deliberate absence of an edit tool to preserve the confirmation flow. No contradiction with 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?

The description is front-loaded with the primary purpose and each subsequent sentence earns its place: status semantics, call triggers, sibling routing, and the no-edit rationale. It is long but not bloated; every sentence adds necessary decision-making context.

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 low complexity (two optional parameters) and the presence of an output schema and annotations, the description is complete enough. It covers what the tool returns conceptually, when to use it, how statuses behave, and how it relates to apply/delete siblings, so an agent can call it correctly.

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 only 50%, and the description does not mention either parameter (category or workspaceId). It adds no meaning beyond the schema and fails to compensate for the undocumented category parameter, leaving part of the parameter surface unexplained.

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 ('List everything the agent memory system holds') and a clear resource ('agent memory'), and it distinguishes the candidate vs active statuses. This makes it immediately clear what the tool does and separates it from the many other list_* siblings.

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 explicitly says when to call this tool ('when the user asks what the AI has learned, what notes are pending, or wants to review its memory') and names the apply/delete sibling tools as alternatives. It also explains why there is no edit tool, giving the agent clear routing and replacement guidance.

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