Meta Ads MCP

update_ad

Modify Meta Ads campaign settings including status, bid amount, creative content, and tracking specifications to optimize performance.

Instructions

Update an ad with new settings.

Args:
    ad_id: Meta Ads ad ID
    status: Update ad status (ACTIVE, PAUSED, etc.)
    bid_amount: Bid amount in account currency (in cents for USD)
    tracking_specs: Optional tracking specifications (e.g., for pixel events).
    creative_id: ID of the creative to associate with this ad (changes the ad's image/content)
    access_token: Meta API access token (optional - will use cached token if not provided)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ad_id`	Yes
`status`	No
`bid_amount`	No
`tracking_specs`	No
`creative_id`	No
`access_token`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 7, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Update' implies mutation, the description doesn't specify permission requirements, whether changes are reversible, rate limits, error conditions, or what happens to existing ad settings not mentioned. For a mutation tool with 6 parameters and no annotation coverage, this is a significant gap in behavioral context.

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 efficiently structured with a clear purpose statement followed by well-organized parameter explanations. Every sentence earns its place, and the bullet-point style for parameters makes it scannable. No wasted words or redundant information is present.

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?

Given this is a mutation tool with 6 parameters, no annotations, but with an output schema (which means return values are documented elsewhere), the description is moderately complete. It covers parameter semantics well but lacks behavioral context, usage guidelines, and differentiation from siblings. The presence of an output schema helps, but for a complex update operation, more contextual information would be beneficial.

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?

The description provides excellent parameter semantics despite 0% schema description coverage. It clarifies that 'ad_id' is a 'Meta Ads ad ID', 'bid_amount' is 'in account currency (in cents for USD)', 'tracking_specs' are 'Optional tracking specifications (e.g., for pixel events)', and 'creative_id' 'changes the ad's image/content'. This adds substantial meaning beyond the bare schema, though it doesn't cover all parameters equally (status explanation is minimal).

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 clearly states the verb ('Update') and resource ('an ad with new settings'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update_ad_creative' beyond the resource name, missing explicit distinction about what makes this ad update different from creative updates.

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?

No guidance is provided about when to use this tool versus alternatives like 'update_ad_creative' or 'update_adset'. The description lacks context about prerequisites, dependencies, or scenarios where this specific ad update tool is appropriate versus other update operations in the system.

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