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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_campaign_duplicate

Duplicates an existing Facebook campaign for a given location, enabling reuse of campaign settings without rebuilding them.

Instructions

Duplicate campaign Duplicate an existing Facebook campaign Endpoint: POST /ad-publishing/facebook/campaigns/{campaignId}/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": {
      "campaignId": "<campaignId>",
      "body": "<body>"
    },
    "name": "ghl_ad_fb_campaign_duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
campaignIdYesCampaign 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

B3.2/5.0
Behavior3/5

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

Annotations already declare this as a non-readonly, open-world, non-idempotent, non-destructive mutation. The description adds useful invocation context — adPublishing.write scope and the versioned POST endpoint — but does not explain what parts of the campaign are copied, whether the duplicate starts as draft/paused, or what side effects occur beyond the source campaign.

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 and front-loads the action, then supplies endpoint and auth metadata. There is minor repetition between 'Duplicate campaign' and 'Duplicate an existing Facebook campaign,' but no wasted prose.

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?

For a mutation tool with no output schema, the description covers the endpoint and auth scope but omits return behavior — e.g., whether it returns the new campaign ID — and duplication semantics. It is enough to call the tool, not enough to predict the result.

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%, with campaignId and body.locationId already documented. The description adds no parameter meaning beyond the endpoint path, so the schema carries the semantic load.

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?

The description states a specific verb and resource: duplicate an existing Facebook campaign. The campaign resource implicitly separates it from sibling tools like ghl_ad_fb_ad_duplicate and ghl_ad_fb_adset_duplicate, but no alternative is explicitly named.

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?

The description gives the endpoint and OAuth scope but no guidance on when to use this tool versus ghl_ad_fb_campaign_upsert, ghl_ad_fb_campaign_publish, or other campaign siblings. The agent must infer usage from the tool name alone.

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