campaignstack

Get accounts

campaignstack_get_accounts

Read-onlyIdempotent

Read one or many connected accounts. LinkedIn rows include safety by default because it gates outreach; maintenance is opt-in and bounded. Google rows omit LinkedIn-only safety, budgets and ramp fields and carry schedulingHours (meeting hours, default 9 to 18). Results are one page. When pagination reports more, say so rather than presenting the page as the whole set, and page through before counting anything.

Input Schema

Name	Required	Description
`ids`	No
`limit`	No
`cursor`	No
`include`	No
`platform`	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.

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 changedSep 29, 2026

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.7/5.0

Behavior4/5

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

Annotations already declare a safe, idempotent read, yet the description adds real substance: platform-dependent row shapes (Google rows omit LinkedIn safety/budget/ramp and add schedulingHours with a 9–18 default), safety included by default, and maintenance opt-in and bounded. The "bounded" claim is left vague, keeping it short of a 5.

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?

The purpose is front-loaded in the first sentence and each subsequent sentence carries a distinct payload about inclusion defaults, platform shape, and pagination. It is dense but free of filler; the pagination advice is slightly over-worded.

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 needn't be spelled out, and the description covers the important platform-conditional shape and the one-page/pagination caveat. It is still thin on the lookup-by-ids path and the practical limits of limit/cursor for a 6-parameter tool.

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 coverage is only 17%, so the description needs to compensate; it does explain include.safety (on by default) and include.maintenance (opt-in, bounded) and implicitly the platform split. It says nothing about ids (max 25), limit (max 50), or how cursor relates to "results are one page," leaving half the parameters unexplained.

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?

"Read one or many connected accounts" gives a clear verb and resource plus the single-vs-bulk scope. It does not differentiate itself from nearby siblings like campaignstack_get_identities or campaignstack_edit_account, so the agent must infer the boundary.

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 implies when the tool applies (reading connected accounts) and gives operational guidance about paging through results before counting. It never states when to prefer this over alternatives such as get_identities, or when to look up by ids versus listing.

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?