Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_email_list_workflow_campaigns

Read-onlyIdempotent

List workflow campaigns for a location, with optional status and search filters plus limit/offset pagination to retrieve and page through results.

Instructions

List Workflow Campaigns Get list of workflow campaigns for a location Endpoint: GET /emails/locations/{locationId}/campaigns/workflows (Version header: v3; source: v3/emails-v3.json) Requires a Sub-Account (location) token. OAuth scopes: emails/campaigns.readonly Pagination params: limit, offset — pass them to page through full result sets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locationId": "<locationId>"
    },
    "name": "ghl_email_list_workflow_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of campaigns to return. Defaults to 10, minimum is 1, maximum is 20
offsetNoNumber of items to skip for pagination. Defaults to 0, minimum is 0
searchNoSearch query to filter campaigns.
statusNoFilter by campaign status
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the required token type (Sub-Account/location), the OAuth scope, and that limit/offset are the pagination mechanism for retrieving full result sets. Return shape and rate-limit behavior are not disclosed.

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 purpose, then auth, then pagination — a sensible ordering. The 'Version header: v3; source: v3/emails-v3.json' provenance line is low-value for an agent selecting or calling the tool, but the rest is tight.

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-only, fully-specified-parameter list endpoint with annotations covering safety, the description supplies the two things the structured data does not: the required token/scope and the pagination contract. Only the response shape and page-size defaults are absent, and those are largely covered by the schema.

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 100%, so all five parameters (including search and status enum) are already documented in the schema; baseline is 3. The description only restates limit/offset as pagination params and adds no syntax or filtering semantics beyond the schema.

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?

States a specific verb+resource: 'List Workflow Campaigns' for a location, and the endpoint path confirms the resource collection. It implicitly distinguishes itself from ghl_email_list_campaigns and ghl_email_list_bulk_action_campaigns by naming 'workflow campaigns', but never explicitly says how it differs from those siblings.

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?

Provides useful invocation context (requires a Sub-Account/location token, needs the emails/campaigns.readonly scope, use limit/offset to page through results), which implies when the tool is callable. However, it never states when to use this tool versus ghl_email_list_campaigns, ghl_email_list_bulk_action_campaigns, or ghl_email_get_workflow_campaign — the closest siblings.

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

Deploy Server

Other Tools