GoHighLevel MCP

ghl_list_faqs

List all FAQ question-answer pairs from a GoHighLevel knowledge base using cursor-based pagination. Retrieve count, hasMore, and lastFaqId to fetch the next page.

Instructions

List all FAQ question/answer pairs for a knowledge base with cursor-based pagination. Returns count, hasMore, lastFaqId for next page.

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": {
      "knowledgeBaseId": "<knowledgeBaseId>"
    },
    "name": "ghl_list_faqs"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max FAQs to return per page (default 10)
`lastFaqId`	No	Last FAQ ID from the previous page — pass to get the next page (cursor pagination)
`knowledgeBaseId`	Yes	Knowledge base ID to fetch FAQs from

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explicitly mentions cursor-based pagination and the return fields (count, hasMore, lastFaqId), which is valuable beyond the schema and gives the agent a clear idea of the operation's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is two sentences, front-loaded with the primary purpose and followed by pagination details. Every sentence contributes useful information without redundancy.

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

Completeness5/5

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

Given the tool's simplicity (3 params, no output schema), the description covers the essential aspects: what is listed, pagination method, and return values. This is complete enough for an agent to invoke the tool correctly without additional context.

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 coverage is 100%, with all three parameters described in the input schema. The description adds high-level pagination context but does not add parameter-specific meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description clearly states the tool lists all FAQ question/answer pairs for a knowledge base, using a specific verb ('List') and resource ('FAQ question/answer pairs'). It distinguishes itself from sibling create/update/delete FAQ tools and includes pagination context.

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 implies usage when one needs to list FAQs for a knowledge base, with clear pagination behavior. It does not explicitly state when not to use it or name alternatives, but the context is clear enough for an agent to select this tool.

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

Deploy Server