GoHighLevel MCP

ghl_create_knowledge_base

Create a new knowledge base for a GoHighLevel location. Provide a name and optional description to receive the created knowledge base object.

Instructions

Create a new knowledge base for the location. Max 15 knowledge bases per location. Returns the created KB object.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Name for the new knowledge base
`description`	No	Optional description for the knowledge base

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosure. It adds valuable behavioral context: the mutation is implied by 'Create', the per-location limit of 15 is a critical constraint, and the return value (created KB object) is explicitly stated. This exceeds the bare minimum for a create operation.

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 long and front-loaded with the action verb. It conveys purpose, constraint, and return value without wasted words. Every sentence adds value and the structure is clear.

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?

For a simple create tool with two documented parameters and no output schema, the description is sufficient. It states the operation, the location scope, the limit, and the return object. The content fully covers what an agent needs to invoke and interpret the result correctly.

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?

The input schema already provides 100% coverage, with descriptions for both 'name' (required) and 'description' (optional). The tool description does not add any parameter-specific details beyond what the schema already contains, 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 uses the specific verb 'Create' and identifies the resource 'knowledge base for the location', clearly stating the action and scope. It distinguishes from sibling tools like list/get/update/delete by naming the create operation explicitly.

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?

The description implies usage via the verb 'Create' and mentions the location scope, but it does not explicitly compare to alternatives or state when not to use the tool. The constraint 'Max 15 knowledge bases per location' provides context but no direct guidance on selecting this over other KB operations.

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

Deploy Server