Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

update

Edit campaign, ad set, or ad fields such as budget, targeting, or name without changing status; explicit user confirmation is required before changes apply.

Instructions

Update fields of a campaign, ad set, or ad, for example budget, targeting, or name. Does not change status; use set_status. 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>",
      "params": "<params>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Meta object ID.
paramsYesMarketing API fields for the object. Nested objects and arrays are JSON-encoded by the server. Budgets are in the minor unit of the account currency.
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

A4.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world, non-destructive operation. The description adds important behavioral context by requiring explicit user confirmation and excluding status changes, though it does not discuss reversibility or response behavior.

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 two sentences with no wasted wording. The scope is front-loaded, followed by the status exclusion and confirmation requirement.

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

Completeness5/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 fully described input schema and safety annotations, the description covers the core operation, the key alternative for status changes, and the confirmation prerequisite. Nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents id, params, change_summary, and user_confirmed in detail. The description adds useful examples of updatable fields such as budget, targeting, and name, but does not add parameter-specific constraints beyond that.

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 a specific verb and resource: update fields of a campaign, ad set, or ad, with concrete examples like budget, targeting, and name. It also distinguishes this operation from set_status, so an agent can identify the tool without opening the schema.

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

Usage Guidelines5/5

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

It explicitly states a when-not-to-use condition: does not change status, use set_status instead. It also adds the prerequisite of explicit user confirmation, leaving little ambiguity about when this tool is appropriate.

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