Skip to main content
Glama

Get workflows

campaignstack_get_workflows
Read-onlyIdempotent

Read one or many workflows in a stable envelope. 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. Includes can add graph, stats, bounded split optimization history, node activity, and leads at nodes.

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

Input Schema

NameRequiredDescriptionDefault
idsNoWorkflow ids to hydrate. Omit to list workflows in the workspace or campaign.
limitNoMaximum items to return, capped at 100.
nodesNo
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
    • 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"
      +}
  2. 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."
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower, and the description still adds real value: both list and hydrate paths return the same collection envelope, and large or computed includes must respect documented caps and must surface truncation/pagination. It does not discuss authorization or the workspace-binding requirement, but the schema covers that.

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?

Five sentences, front-loaded with the core verb and the ids rule, with no filler. A couple of clauses are slightly redundant ("The response still uses the same collection envelope" partly restates "stable envelope"), but nothing is wasted overall.

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 seven-parameter, deeply nested reader with an output schema available, the description covers what an agent must know before calling: list-vs-hydrate, include discipline, caps, and truncation reporting. Return-value detail is legitimately delegated to the output schema, so the remaining omissions are minor.

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?

With 57% schema coverage, the description usefully compensates on the two most complex parameters: ids mode semantics and the include payload options (graph, stats, bounded split optimization history, node activity, leads at nodes) with their cap-and-truncation obligations. It adds nothing for limit, cursor, filters, or workspaceId, which the schema already documents in detail.

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 workflows in a stable envelope" pairs a specific verb (read) with a specific resource (workflows) and immediately disambiguates the two modes: omit ids to list, pass ids to hydrate. It never names a sibling or explains how it differs from adjacent readers like campaignstack_get_workflow_node_types, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete selection rules for the ids parameter (omit = list, one = single record, several = several records) and a clear usage constraint for includes ("Use include only for extra details the user asked for"), which meaningfully shapes when to expand payloads. It offers no explicit when-not guidance or named alternatives, which keeps it out of 5 territory.

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