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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_account_delete

DestructiveIdempotent

Removes a LinkedIn ad account connection from a GoHighLevel location using location and ad account IDs. Use to disconnect ad publishing access; endpoint is deprecated in favor of v4.

Instructions

Delete ad account Remove a LinkedIn ad account connection from a location. Deprecated: use DELETE /ad-publishing/linkedin/ad-accounts/{adAccountId} with header version: v4. Endpoint: DELETE /ad-publishing/linkedin/ad-account (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": {
      "locationId": "<locationId>",
      "adAccountId": "<adAccountId>"
    },
    "name": "ghl_ad_li_account_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation identifier
adAccountIdYesAd account identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, so the safety profile is known. The description adds real context beyond that: the required OAuth scope (adPublishing.write), the deprecation status, and the underlying endpoint/version, which lets an agent know it needs write auth and that a newer API path exists.

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, then the scope/deprecation caveats. Slight redundancy between the title line 'Delete ad account' and the body sentence, plus boilerplate source metadata, but nothing is padded.

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?

Two required params, no output schema, and annotations that already encode safety. With endpoint, version, scope and deprecation all disclosed, an agent has everything needed to decide whether and how to call it; only the side effects of removing the connection are left implicit.

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 both locationId and adAccountId, so the schema carries parameter meaning. The description only re-surfaces adAccountId as a path variable in the replacement endpoint, adding nothing new about formats or constraints.

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 (delete/remove) and resource (LinkedIn ad account connection at a location), and the 'LinkedIn' qualifier clearly separates it from siblings like ghl_ad_fb_account_delete and ghl_ad_google_account_delete.

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 deprecation note explicitly steers the agent to the v4 endpoint instead of this v3 one, which is valuable routing. It does not say how to obtain the adAccountId (e.g. via ghl_ad_li_account_list) or warn about what else is affected, so it falls short of full when/when-not guidance.

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