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

ghl-mcp-server-v2

by zackscriven

ghl_funnel_list

Read-onlyIdempotent

Retrieve and page through all funnels for a GoHighLevel sub-account using location, name, type, category, parent, offset, and limit filters.

Instructions

Fetch List of Funnels Retrieves a list of all funnels based on the given query parameters. Endpoint: GET /funnels/funnel/list (Version header: v3; source: v3/funnels-v3.json) Requires a Sub-Account (location) token. Pagination params: offset, limit — 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_funnel_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
typeNo
limitNo
offsetNo
categoryNo
parentIdNo
locationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds concrete operational context the annotations do not: the endpoint, a required v3 version header, and that a Sub-Account (location) token is required. It stops short of describing response shape or how filters combine.

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?

Short and front-loaded: the purpose appears first, followed by endpoint/auth/pagination notes. The endpoint path and source-file metadata are slightly noisy, but they earn their place as invocation context.

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?

For a list tool with seven parameters and no output schema, the description should explain what the filters mean and what the result contains. It covers auth and pagination adequately but leaves the majority of filter parameters and the return structure unaddressed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it only covers offset and limit. The other five filters (name, type, category, parentId, and the required locationId) are undocumented in both schema and description, leaving the agent to guess their semantics.

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 and resource ('Fetch / Retrieves a list of all funnels'), which is unambiguous and distinct from funnel siblings like get_pages_by_id or create_redirect. It does not explicitly name those siblings, but the read-list intent is clear from the first sentence.

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?

It notes that results are driven by query parameters and that offset/limit page through full result sets, which implies how to use it. However, there is no explicit guidance on when to choose this over alternatives such as get_pages_by_id, nor any exclusions or prerequisites beyond auth.

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