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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_ad_duplicate

Duplicate an existing Facebook ad in GoHighLevel by providing the ad ID and location ID, enabling quick reuse of ad settings for new campaigns.

Instructions

Duplicate ad Duplicate an existing Facebook ad Endpoint: POST /ad-publishing/facebook/ads/{adId}/duplicate (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_duplicate"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body
      Added value: +{
      +  "description": "Request body (schema carried verbatim from the official OpenAPI spec).",
      +  "properties": {
      +    "locationId": {
      +      "description": "Location identifier",
      +      "example": "HChooFuiyPpVYzeJ4HMe",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "locationId"
      +  ],
      +  "title": "LocationIdBodyDTO",
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "adId"
      -]New value: +[
      +  "adId",
      +  "body"
      +]
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is known. The description adds useful operational context (POST endpoint, v3 header, adPublishing.write scope) but omits key behavior: whether the copy is created paused/draft, what naming it receives, and that it requires write access to the ad account.

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 verb+resource, and the endpoint/scope lines are dense and useful. Minor waste in the duplicated 'Duplicate ad' title line immediately restating the noun phrase that follows, but overall no sentences to cut.

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

Completeness3/5

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

With no output schema, the description should say what a duplicate returns (a new ad id, presumably), and it does not. For a mutating tool that produces a new resource, omitting the return value and the copy's initial state leaves a real gap, though the endpoint and scope lines partially compensate.

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 adId and the nested body.locationId are already documented, setting the baseline at 3. The description adds no extra meaning about these parameters — notably it never explains that locationId in the body must match the owning location of the ad being duplicated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Duplicate') and resource ('an existing Facebook ad'), which is unambiguous against siblings like ghl_ad_fb_ad_upsert or ghl_ad_fb_ad_delete. However, it does not differentiate itself from the structurally similar ghl_ad_fb_adset_duplicate and ghl_ad_fb_campaign_duplicate beyond the noun 'ad', leaving the level distinction to the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus creating a new ad, upserting, or duplicating an adset/campaign. The only context given is the endpoint path and OAuth scope, which describe mechanics rather than selection 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