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

ghl-mcp-server-v2

by zackscriven

ghl_kb_faq_delete

DestructiveIdempotent

Permanently deletes an outdated knowledge base FAQ by ID. Remove canned answers no longer needed; use update to revise an FAQ instead.

Instructions

Delete an existing knowledge base FAQ Permanently deletes one FAQ from a knowledge base. WHEN TO USE: use this when a canned answer is outdated; use update to revise it instead; use list to find the FAQ id. RETURNS: whether the delete succeeded. Endpoint: DELETE /knowledge-bases/faqs/{id} (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": {
      "id": "<id>"
    },
    "name": "ghl_kb_faq_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesfaq ID as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds meaningful extra context anyway: the word "Permanently" signals irreversibility, plus the Sub-Account (location) token requirement and the knowledge-bases.write OAuth scope, which determine whether the call will even be authorized. The endpoint and API version header are also disclosed.

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 and labeled with a consistent WHEN TO USE / RETURNS structure, so an agent can scan it quickly. The trailing endpoint metadata line, particularly the source file reference, is scaffolding rather than guidance an agent needs to decide or invoke, which keeps it off a 5.

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 single-parameter destructive tool with no output schema, everything needed is present: what it deletes, that it is permanent, how to get the id, the return value (success flag), plus auth and scope requirements. There is no output schema burden to compensate for.

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

Parameters4/5

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

There is only one parameter and the schema already documents it at 100% coverage, so the baseline would be 3. The description earns above baseline by telling the agent where the id comes from (use list to find the FAQ id), which is genuine operational meaning the schema does not provide.

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 ("Permanently deletes one FAQ from a knowledge base") and scopes it to a single object rather than a bulk operation. The naming of the knowledge-base FAQ entity clearly separates it from sibling tools like ghl_kb_delete_knowledge_base, ghl_kb_delete_file and ghl_kb_faq_update.

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 line gives the trigger condition (a canned answer is outdated) plus two explicit alternative branches: use update to revise rather than delete, and use list to resolve the id. That is exactly the when/when-not/alternatives structure expected, with nothing left to inference.

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