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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_ad_status_update

Pause, resume, or archive a LinkedIn ad, campaign, or ad group by updating its status through the GoHighLevel ad publishing API.

Instructions

Update ad status Pause or resume a LinkedIn ad, campaign, or ad group. Deprecated: use PATCH /ad-publishing/linkedin/ads/{adId}/status with header version: v4. Endpoint: PATCH /ad-publishing/linkedin/{adId}/status (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>",
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_ad_li_ad_status_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"LinkedInUpdateAdStatusBodyDTO"
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
  2. 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 readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the description's extra value is the required OAuth scope (adPublishing.write) and the version-header requirement, both of which affect whether the call will succeed. It does not describe side effects of pausing versus archiving, but does not contradict the annotations either.

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 summary sentence and deprecation warning are front-loaded, which is the right ordering. The endpoint line partially duplicates path information already conveyed by the deprecation warning, a small amount of redundancy but nothing egregious.

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 mutation tool with full annotation coverage, complete schema documentation, and no output schema, the description supplies the missing operational context: auth scope and the required API version header. The only remaining gap is that it does not disclose what happens to an ad when paused or archived.

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 all three parameters are already documented in the schema. The description contributes only a loose restatement ('ad, campaign, or ad group') that mirrors the body.type enum without adding format or constraint detail, so it stays at the baseline.

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?

The description opens with a specific verb and resource ('Update ad status') and immediately narrows the scope to LinkedIn ads, campaigns, and ad groups, which cleanly separates it from the many ghl_ad_fb_* and ghl_ad_google_* siblings. The 'pause or resume' phrasing is slightly narrower than the operationType enum (which also allows ARCHIVED), but the core purpose is unmistakable.

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 tells the agent this is the older path and names the newer endpoint to prefer, which is a genuine usage signal. It stops short of naming a callable MCP alternative (the suggested replacement is a raw PATCH path rather than a sibling tool), so there is no concrete 'use tool X instead' routing.

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