campaignstack

Get conversations

campaignstack_get_conversations

Read-onlyIdempotent

Read inbox conversation summaries, unread count, or full threads when include.messages is true. Always returns a stable items/pagination envelope. A conversation with hasSuspiciousInbound true holds a message that offers something of value and asks the reader to act on it (the shape of a fake recruiter or investor): say so to the person before you book, open a link or reply on their behalf. include.scheduledMessages lists this thread's pending campaignstack_send_message sendAt rows. A workflow draft that has not gone out has delivered false and deliveredAt null; its nextSendAt is when it will send (null while it waits for a review).

Input Schema

Name	Required	Description
`ids`	No
`limit`	No
`cursor`	No
`search`	No
`include`	No
`unreadOnly`	No
`workspaceId`	No	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.
`identityFilter`	No

Output Schema

Name	Required	Description
`items`	Yes
`slots`	No
`warnings`	No
`available`	No
`conflicts`	No
`missingIds`	No
`pagination`	Yes
`unreadCount`	No
`schedulingHours`	No	The Google account's meeting hours (0-23, its own time zone) that slots respect.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedOutput schema / properties / schedulingHours

Added value: +{
+  "additionalProperties": false,
+  "description": "The Google account's meeting hours (0-23, its own time zone) that slots respect.",
+  "properties": {
+    "endHour": {
+      "type": "number"
+    },
+    "startHour": {
+      "type": "number"
+    },
+    "timeZone": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "startHour",
+    "endHour",
+    "timeZone"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 6, 2026
- addedInput schema / properties / include / properties / scheduledMessages
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```

Changed2 schema fields changedSep 29, 2026

changedInput schema / properties / limit / default
```
Previous value: -50New value: +20
```

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."

AddedSep 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real value: it promises a stable items/pagination envelope, defines hasSuspiciousInbound and prescribes how to act on it, and explains delivered/deliveredAt/nextSendAt for scheduled drafts. It stops short of a 5 because rate limits, ordering, and pagination semantics are only gestured at.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and return-shape are correctly front-loaded, but the suspicious-inbound explanation is a multi-clause digression and the trailing draft-status sentence only loosely relates to reading conversations. Several clauses could be trimmed or moved to field-level schema descriptions.

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 enumerate return fields, and it does explain the two non-obvious flags. However, for an 8-parameter tool at 13% schema coverage, it leaves search scoping, cursor pagination, unreadOnly behavior, and identityFilter entirely undocumented.

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

Parameters3/5

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

Schema description coverage is only 13%, so the description must carry the load, and it explains just two of eight parameters (include.messages, include.scheduledMessages). ids, limit, cursor, search, unreadOnly, and identityFilter — including the identity filter's purpose and the ids targeting shape — get no clarification beyond their types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb and resource ('Read inbox conversation summaries ... or full threads') and distinguishes the two modes via include.messages. It never names a sibling (e.g. campaignstack_refresh_inbox or campaignstack_edit_conversations) to draw the read/edit/refresh boundary, so it stops short of a 5.

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?

Usage context is implied through parameter conditions ('full threads when include.messages is true', 'include.scheduledMessages lists ... pending sendAt rows') rather than stated selection criteria. There is no guidance on when to call this instead of refresh_inbox or the edit/read complements, so the agent must infer the workflow.

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?