Skip to main content
Glama

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "campaignstack_get_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
limitNo
cursorNo
searchNo
includeNo
unreadOnlyNo
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.
identityFilterNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
slotsNo
warningsNo
availableNo
conflictsNo
missingIdsNo
paginationYes
unreadCountNo
schedulingHoursNoThe Google account's meeting hours (0-23, its own time zone) that slots respect.
readAvailabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / readAvailability
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "accounts": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "warning": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "warning",
      +    "accounts"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • 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"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / include / properties / scheduledMessages
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  4. Changed2 schema fields changed
    • 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."
  5. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description is free to add interpretation: it promises a stable items/pagination envelope, defines hasSuspiciousInbound as a fake-recruiter/investor signal with an instruction to warn the user before acting, and explains the draft semantics of delivered/deliveredAt/nextSendAt. That is substantive context beyond the annotations, with only pagination limits left implicit.

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?

Front-loads the core purpose in the first sentence and keeps the return-envelope promise immediately after. The safety paragraph is long but earns its length by changing agent behavior; only the draft-field sentence feels closer to edge-case documentation than core instruction.

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 values need not be re-explained, yet the description still supplies envelope stability and field meaning that the schema cannot convey. The main gap is the undocumented filter and pagination parameters, which matter for an eight-parameter tool with no required fields and a default limit.

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%, with workspaceId the sole documented parameter, so the description must compensate. It does explain include.messages and include.scheduledMessages in real depth, but ids, search, cursor, limit, unreadOnly and identityFilter get no mention, leaving most of the eight parameters to be read off bare schema 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?

Names a specific verb and resource (read inbox conversation summaries) and enumerates the three concrete modes: summaries, unread count, full threads with include.messages. It distinguishes itself from campaignstack_send_message by framing scheduledMessages as that tool's pending sendAt rows, though it never explicitly contrasts with campaignstack_edit_conversations.

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 is implied through parameter conditions ('full threads when include.messages is true', 'include.scheduledMessages lists ... pending rows') rather than stated as when-to-use-this-vs-that guidance. There is no exclusion rule for the write-side siblings, so an agent must infer that reads belong here and mutations elsewhere.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources