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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_ad_delete

DestructiveIdempotent

Delete a Facebook ad by ID and location to remove outdated or incorrect campaigns from GoHighLevel ad publishing.

Instructions

Delete ad Delete a Facebook ad by ID Endpoint: DELETE /ad-publishing/facebook/ads/{adId} (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": {
      "adId": "<adId>",
      "body": "<body>"
    },
    "name": "ghl_ad_fb_ad_delete"
  }
}

Input Schema

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

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, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds value beyond that with the OAuth scope requirement (adPublishing.write), the exact endpoint path, and the API version header, which help an agent understand auth and routing needs.

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?

The description is short, front-loaded with the action, then the endpoint and auth scope. The opening line 'Delete ad' slightly repeats 'Delete a Facebook ad by ID,' but nothing else is wasteful.

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 2-parameter destructive mutation with no output schema, the description supplies endpoint, version, and OAuth scope, and annotations cover safety semantics. It could be more complete by explaining the required locationId in the body and whether the deletion is permanent, but nothing critical 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%, so adId and the nested body.locationId are already documented in the schema. The description adds no meaning about either parameter (e.g., why a delete requires a locationId), so it sits at the baseline for fully-covered schemas.

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 Facebook ad by ID') and scopes it to the Facebook ad surface, which separates it from the Google/LinkedIn ads and from siblings like ghl_ad_fb_ad_pause, ghl_ad_fb_ad_upsert, and ghl_ad_fb_ad_duplicate. The agent can identify the operation without opening the 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 intent to delete is implied, but the description never says when to delete versus pausing/resuming an ad (ghl_ad_fb_ad_pause, ghl_ad_fb_ad_resume) or whether deletion is permanent or recoverable. It also doesn't name alternatives explicitly, unlike a top-tier definition that routes the agent.

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