Skip to main content
Glama
Sign In
GoHighLevel MCP

GoHighLevel MCP

by NerdSnipe-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ghl_delete_knowledge_base

Permanently delete a knowledge base and all its content, including FAQs and trained URLs. Returns success confirmation.

Instructions

Permanently delete a knowledge base and all its content (FAQs, trained URLs, etc.). Returns { success: true } on success.

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

Input Schema

NameRequiredDescriptionDefault
knowledgeBaseIdYesThe knowledge base ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

A4.3/5.0
Behavior4/5

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

The description discloses that deletion is permanent, cascades to all content, and returns a success object. With no annotations, this provides essential behavioral context, though it lacks auth prerequisites or error handling details.

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?

A single, information-dense sentence. It front-loads the purpose and includes key behavioral details without any fluff.

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 destructive tool with one parameter and no output schema, the description covers the action, the scope of deletion, permanence, and the return value. This is complete and self-sufficient.

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 schema already fully describes the single parameter (knowledgeBaseId). The description adds no additional meaning beyond what is in the schema, so a baseline score of 3 is appropriate given 100% schema coverage.

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 verb 'delete' with the resource 'knowledge base' and specifies it deletes all content including FAQs and trained URLs. This differentiates it from sibling tools like delete_faq which deletes a single FAQ.

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 context is clear: this tool removes an entire knowledge base and its contents. While it doesn't explicitly say 'use this instead of delete_faq', the scope is unambiguous enough for an agent to select it correctly.

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