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

ghl-mcp-server-v2

by zackscriven

ghl_kb_delete_knowledge_base

DestructiveIdempotent

Permanently deletes a knowledge base and its trained content when the entire knowledge source is no longer needed. Returns whether the deletion succeeded.

Instructions

Delete a knowledge base Permanently deletes a knowledge base and its associated trained content. WHEN TO USE: use this when the whole knowledge source is no longer needed; use deleteTrainedUrlsForKnowledgeBase or delete (FAQ) to remove only some content. RETURNS: whether the delete succeeded. Endpoint: DELETE /knowledge-bases/{knowledgeBaseId} (Version header: v3; source: v3/knowledge-base-v3.json) Requires a Sub-Account (location) token. OAuth scopes: knowledge-bases.write

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

Input Schema

NameRequiredDescriptionDefault
knowledgeBaseIdYesThe unique identifier of the knowledge base to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / knowledgeBaseId / description
      Added value: +"The unique identifier of the knowledge base to delete"
    • addedInput schema / properties / knowledgeBaseId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
  2. First observedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the cascade effect ('permanently deletes... its associated trained content'), the required Sub-Account/location token, the OAuth scope knowledge-bases.write, and the return signal. This is exactly the context annotations cannot convey.

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?

Front-loaded with purpose, then usage, returns, and auth in a predictable order; the WHEN TO USE clause earns its space. Minor waste in the trailing metadata ('source: v3/knowledge-base-v3.json') that adds little for an agent.

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?

Covers everything an agent needs for a destructive one-param tool: irreversible cascade scope, auth/token requirement, scopes, and success signal, with no output schema to fill in. Nothing material is missing.

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% for the single knowledgeBaseId parameter, so the schema already carries the meaning. The description only echoes the id via the endpoint path and adds no format, sourcing, or lookup guidance beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Delete a knowledge base') and immediately disambiguates from partial-removal siblings. An agent can tell this apart from ghl_kb_crawler_delete_urls or ghl_kb_faq_delete without opening any schema.

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

Usage Guidelines5/5

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

The WHEN TO USE block gives an explicit positive condition ('when the whole knowledge source is no longer needed') and names the alternatives for the narrower case ('deleteTrainedUrlsForKnowledgeBase or delete (FAQ)'). Exclusions and alternatives are both stated.

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