Skip to main content
Glama

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.

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_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
limitNo
cursorNo
includeNo
platformNo
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
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
    • 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."
  4. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantial context beyond them: LinkedIn rows include safety by default, maintenance is opt-in and bounded, Google rows omit LinkedIn-only safety, budget and ramp fields, and carry schedulingHours defaulting to 9–18. It also discloses the one-page result behavior and instructs the agent to page through and report truncation before counting.

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 core read scope is front-loaded and the sentences are dense with distinct facts rather than filler. Some phrasing is roundabout ('say so rather than presenting the page as the whole set'), but no sentence is redundant.

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 rich annotations and an output schema present, the description needn't explain return shapes, and it covers the important behavioral differentiators (platform field differences, opt-in maintenance, single-page paging). The remaining gap is parameter-level detail for ids, limit and cursor.

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 17% (only workspaceId is documented), so the description must compensate. It does explain the platform split and the include.safety / include.maintenance defaults, which is real value, but it never mentions the ids max of 25, the limit cap of 50, or cursor semantics, leaving key constraints to the schema alone.

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 gives a specific verb and resource — 'Read one or many connected accounts' — and the 'one or many' phrasing maps to the ids/batch capability. It is clearly a read tool, distinguishing it from the sibling campaignstack_edit_workspace_accounts by implication, though it never names that sibling explicitly.

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 rather than stated: safety is on 'because it gates outreach' and maintenance is 'opt-in and bounded', which hints at when those flags matter, but there is no explicit 'use this when…' guidance or a named alternative. The pagination instruction tells the agent how to behave, not when to choose this tool over another.

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