Skip to main content
Glama

Get workspaces

campaignstack_get_workspaces
Read-onlyIdempotent

Read workspaces and optional workspace details in one stable collection envelope. Use this when the user needs workspace identity, settings, members, billing, credits, metrics, setup, branding, compliance, playbook, playbook history, or the pending playbook proposal. Omit ids to list matching records, pass one id for one record, or pass several ids for several records. The response still uses the same collection envelope. Use include only for extra details the user asked for. Large, computed, historical, or external includes must use their documented caps and must report when data is truncated or paginated. This read-only tool does not change data. Instead use campaignstack_get_campaigns for campaign setup, and campaignstack_get_identities for account or voice ownership. The result returns items, pagination, missingIds when requested ids are unavailable, and warnings for capped includes.

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

Input Schema

NameRequiredDescriptionDefault
idsNoOptional entity ids to fetch, capped at 25.
limitNoMaximum items to return, capped at 50.
cursorNoOpaque pagination cursor.
filtersNo
includeNo
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
itemsNo
warningsNo
missingIdsNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include / properties / billing / description
      Previous value: -"Workspace billing state."New value: +"Workspace billing state: plan, paid tier (starter, pro or max, null off a subscription), limits including the monthly credit pool, billing cycle and renewal."
  2. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "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.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / include / properties / playbook / description
      Previous value: -"Current workspace playbook."New value: +"Current workspace playbook: sections, outreach intents, capabilities, and the company context. companyProfile holds each fact field with its source (site = read off the website, user = stated by a person, agent = stated by an agent, linkedin = from the LinkedIn page); offerContext is the user's free text; companyContext is the composed text every message carries, with its length and the cap it is checked against."
  4. Changed1 schema field changed
    • addedInput schema / properties / include / properties / checklist
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Setup rewards: each step, its credits, whether it is claimed, and how to complete it.",
      +  "properties": {},
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / filters / 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."
  6. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the "does not change data" sentence adds little; that line is close to restating structured data. The genuinely additive content is the disclosure that large/computed/historical/external includes are capped and must report truncation or pagination, plus missingIds and warnings in the result — useful behavior an agent could not infer from the annotations.

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?

Front-loaded and largely purposeful, but a few sentences are filler or repetition: "This read-only tool does not change data" duplicates the annotations, and "The response still uses the same collection envelope" restates the opening sentence. The long comma-separated enumeration of facets is dense but does carry information.

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?

For a read tool with annotations and a full output schema, the description covers selection semantics, include guidance, caps/truncation behavior and cross-references to siblings. Return-value detail (items, pagination, missingIds, warnings) is arguably redundant with the output schema, but nothing an agent needs to invoke it correctly appears to be missing.

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

Parameters4/5

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

The schema is already well documented (67% coverage, rich per-include descriptions), so the description's contribution is mostly the ids cardinality semantics — list vs single vs multiple, all returning the same collection envelope — which sharpens how the optional ids array is meant to be used. It does not add further syntax detail for limit, cursor, or filters, but those are adequately covered in the schema.

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?

States a specific verb+resource ("Read workspaces and optional workspace details") and enumerates the detail facets reachable through include, so an agent knows exactly what the tool returns. It explicitly differentiates from siblings by naming campaignstack_get_campaigns and campaignstack_get_identities as the tools for campaign setup and account/voice ownership.

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?

Gives concrete selection rules: omit ids to list, one id for a single record, several ids for several records, and reserve include for details the user actually asked for. It also names the alternatives to use for campaign and identity questions, so both when-to-use and when-not-to-use are covered explicitly.

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