Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

set_status

Destructive

Change a Meta campaign, ad set, or ad to ACTIVE, PAUSED, or ARCHIVED while requiring explicit user confirmation before any ad spend starts.

Instructions

Set a campaign, ad set, or ad to ACTIVE, PAUSED, or ARCHIVED. ACTIVE starts ad spend and needs its own explicit confirmation after the user reviewed the object.

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>",
      "status": "<status>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "set_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Meta object ID.
statusYes
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.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the bar is lower, but the description still adds material facts beyond them: ACTIVE starts ad spend (a financial side effect) and requires its own explicit confirmation after user review. It omits whether ARCHIVED is reversible or whether archiving stops delivery permanently, which keeps it from a 5.

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, zero waste, with the operation and its allowed values front-loaded and the risk-bearing ACTIVE caveat immediately after. Every clause earns its place.

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 destructive, non-idempotent mutation with no output schema, the definition covers the biggest hazard (spend activation and confirmation) but leaves reversibility, archiving consequences, and error/return behavior unstated. Adequate to call safely in the common case, incomplete for the risky ones.

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 75% and the enum already documents the three status values. The description reinforces the confirmation requirement that maps to 'user_confirmed' but says nothing about 'change_summary' (that it must record the exact approved change) or warns the agent never to self-assert confirmation. Baseline 3 is appropriate when the schema carries most of the semantics.

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 opens with a specific verb and resource ('Set a campaign, ad set, or ad') and enumerates the reachable states (ACTIVE, PAUSED, ARCHIVED), which cleanly separates it from the generic 'update' sibling. It does not name a sibling or explicitly scope itself as status-only versus other mutable fields, so it stops short of a 5.

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 gives a real precondition for the ACTIVE case ('needs its own explicit confirmation after the user reviewed the object'), which tells the agent when to hold off. However, there is no guidance on when to choose this over 'update' or 'delete', nor on the ARCHIVED path, so usage is only partially implied.

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