Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

copy

Duplicate an existing Meta campaign, ad set, or ad as a paused copy after explicit user confirmation, so you can reuse structure and settings without relaunching spend.

Instructions

Copy a campaign, ad set, or ad. The copy is always PAUSED. Requires explicit user confirmation.

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": {
      "id": "<id>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Meta object ID.
paramsNoCopy parameters, for example campaign_id, adset_id, deep_copy, rename_options.
change_summaryYesConcise exact change the user approved in the current request, with budget and status.
user_confirmedYesMust be true only after explicit action-time user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly=false, idempotent=false, destructive=false, but the description adds two traits they cannot express: the resulting copy is always PAUSED, and the call requires explicit action-time user confirmation. That is meaningful behavioral context beyond structured fields. It does not say whether the copy is deep or shallow by default, which is the remaining behavioral gap.

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?

Two sentences, fully front-loaded: action first, then the safety-relevant state, then the confirmation gate. Nothing is redundant and no sentence is wasted.

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 a nested params object and no output schema, the definition covers action, resulting state, and the confirmation contract, which is what an agent needs to call it safely. It omits what the response returns (e.g., the new object ID) and what deep_copy/rename_options actually change, but those are partly delegated to the schema.

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 the baseline is 3; the schema already explains id, params (campaign_id, adset_id, deep_copy, rename_options), change_summary, and user_confirmed. The description only reinforces the user_confirmed requirement, adding no new semantics for the nested params object.

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 uses a specific verb ('Copy') and enumerates the exact resource types it accepts (campaign, ad set, ad), so the agent knows the object scope without opening the schema. It stops short of naming sibling tools like create or update to explain why copy is the right choice, so it is clear but not fully differentiated.

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?

It states a hard precondition ('Requires explicit user confirmation'), which is real usage guidance, but it never says when to prefer copy over create/update or when copying is inappropriate. The when-to-use signal is implied by the verb rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.