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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_account_delete

DestructiveIdempotent

Remove a Facebook ad account connection from a specified location by providing the ad account ID and location ID in GoHighLevel.

Instructions

Delete ad account Remove a Facebook ad account connection from a location Endpoint: DELETE /ad-publishing/facebook/ad-accounts/{adAccountId} (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.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": {
      "adAccountId": "<adAccountId>",
      "body": "<body>"
    },
    "name": "ghl_ad_fb_account_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
adAccountIdYesAd account identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"LocationIdBodyDTO"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered; the description adds real context beyond that by specifying the required OAuth scope (adPublishing.write) and the exact endpoint/version. It still does not say whether ads/campaigns tied to the account are affected, which is the main remaining behavioral unknown.

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 the action and a clarifying expansion, then the endpoint and scope metadata. The first two lines are slightly redundant, and the OpenAPI source filename is low-value noise, but overall it is tight and scannable.

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

Completeness4/5

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

For a two-parameter destructive tool with full schema coverage, rich annotations and no output schema, the description supplies the missing pieces: auth scope, endpoint verb/path, and the exact meaning of 'delete'. Only the downstream effects on linked campaigns/ads remain unspecified.

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 description coverage is 100%, so both parameters are already documented. The endpoint line confirms adAccountId is a path parameter while locationId travels in the body, which is a small addition the schema does not state, but the description never mentions locationId explicitly.

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, and crucially clarifies the semantics: it removes the *connection* of a Facebook ad account from a location, not the underlying Facebook ad account. That distinction separates it from ghl_ad_fb_account_get/list and from ghl_ad_fb_integration_delete without needing to open a schema.

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 action is unambiguous but there is no explicit when-to-use guidance, no statement of what happens after deletion, and no named alternative (e.g., pause/unlink vs. delete, or the Google/LinkedIn equivalents). Usage is only implied by the verb and the scope line.

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