Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ads_duplicate_campaign

Clone a Meta Ads campaign and, if needed, deep copy all ad sets and ads. Choose whether the duplicate starts PAUSED or ACTIVE and apply a custom suffix.

Instructions

Duplicate a campaign with optional deep copy of all ad sets and ads.

Args: deep_copy: If True, copies all ad sets and ads under the campaign. status_option: PAUSED (recommended) or ACTIVE for the copy. rename_options: Optional dict {"rename_strategy": "DEEP_RENAME", "rename_suffix": " - copy"}.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "ads_duplicate_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
deep_copyNo
campaign_idYes
status_optionNoPAUSED
rename_optionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are present. The description explains deep_copy, status_option, and rename_options behaviors, including a recommended PAUSED status and a dict example. However, the 'confirm' parameter is not disclosed, and there is no info about side effects or return values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a compact docstring with a front-loaded purpose line and an Args block. Every sentence adds relevant detail without fluff.

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 5-parameter tool with no annotations or output schema, the description covers the core options but misses 'confirm' and any information about return values or campaign state after duplication. Adequate but not fully complete.

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 0%, so the description carries the burden. It adds semantics for deep_copy, status_option, and rename_options, but omits 'confirm' and doesn't elaborate on campaign_id. The rename_options example is useful but partially compensates for the coverage gap.

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 states 'Duplicate a campaign with optional deep copy of all ad sets and ads' – a specific verb and resource, clearly distinguishing from sibling duplicate tools for adsets/ads. The scope is explicit and unambiguous.

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?

No explicit guidance on when to choose this vs ads_duplicate_adset or ads_duplicate_ad. The description implies usage by naming the operation and options, but doesn't specify exclusions or alternatives.

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