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

ghl-mcp-server-v2

by zackscriven

ghl_workflow_list

Read-onlyIdempotent

Lists GoHighLevel workflows for a specified sub-account location ID so you can inspect existing automations before validating or publishing definitions.

Instructions

WORKFLOW API — limited availability: enabled for selected sub-accounts only; others get 403 WORKFLOW_API_NOT_ENABLED_FOR_LOCATION (not a token or scope problem). Suggested order: get step types -> build the definition -> validate (validate_workflow_definition, read-only) -> create (always lands in draft) -> publish via update status. Rate limits: integration daily quota + 10s burst (X-RateLimit-* headers) AND a per-sub-account budget per 10s window with reads and writes counted separately; no Retry-After is sent. Logs: default and max range 30 days; retained 60 days. Get Workflow Endpoint: GET /workflows/ (Version header: v3; source: v3/workflows-v3.json) OAuth scopes: workflows.readonly

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

Input Schema

NameRequiredDescriptionDefault
locationIdYesSub-account (location) ID to list workflows for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / locationId / description
      Added value: +"Sub-account (location) ID to list workflows for"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses concrete operational behavior: 403 WORKFLOW_API_NOT_ENABLED_FOR_LOCATION on non-enabled sub-accounts, dual rate-limit regimes (daily quota plus 10s burst with X-RateLimit-* headers, plus a per-sub-account budget counting reads and writes separately), and no Retry-After header. It does not describe pagination or result shape, but the error/limit disclosure is genuinely useful and consistent with 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two-thirds of the text is family-level boilerplate (availability, build pipeline, rate limits, log retention) that is front-loaded ahead of the tool's own purpose. For a single-parameter read, the one useful line about what it does is buried in a middle section.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Operationally the description is rich (availability gating, rate limits, OAuth scope) and there is no output schema to explain, so an agent won't be blocked from calling it. However, it never says what the response contains or whether results are paginated, and the family boilerplate about logs and workflow creation is irrelevant to this call.

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% and the single locationId parameter is already documented as the sub-account to list workflows for. The description adds no format, default, or multi-location semantics beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The actual purpose is only inferable from the endpoint line 'GET /workflows/' and the scope 'workflows.readonly'; the phrase 'Get Workflow' is ambiguous and never states that it returns a collection of workflows for a location. Nothing distinguishes it from close siblings such as ghl_workflow_search, ghl_workflow_get_definition, or ghl_workflow_get_logs, which are all reads in the same family.

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

Usage Guidelines2/5

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

The 'Suggested order' pipeline (get step types -> build -> validate -> create -> publish) is guidance for authoring workflows, not for when to call this list tool. There is no statement of when to list versus search, or of any prerequisite beyond the availability caveat.

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