Skip to main content
Glama
pralayasimha23

meta-ads-mcp

update_ad_creative

Update ad creative names and optimization settings. To change content like headline or images, create a new creative instead.

Instructions

Update an existing ad creative's name or optimization settings.

IMPORTANT — Meta API limitation: The Meta API does NOT allow updating content
fields (message, headline, description, CTA, image, video, URL) on existing
creatives. Only the creative `name` and optimization settings (asset_feed_spec)
can be changed. To change ad content, create a new creative with the desired
content and update the ad to reference the new creative via `update_ad`.

Args:
    creative_id: Meta Ads creative ID to update
    access_token: Meta API access token (optional - will use cached token if not provided)
    name: New creative name (this is the most reliable update)
    message: New ad copy/text — NOTE: Meta API may reject this on existing creatives
    messages: List of primary text variants — NOTE: Meta API may reject this on existing creatives
    headline: Single headline — NOTE: Meta API may reject this on existing creatives
    headlines: New list of headlines — NOTE: Meta API may reject this on existing creatives
    description: Single description — NOTE: Meta API may reject this on existing creatives
    descriptions: New list of descriptions — NOTE: Meta API may reject this on existing creatives
    optimization_type: Set to "DEGREES_OF_FREEDOM" for FLEX (Advantage+) creatives
    dynamic_creative_spec: New dynamic creative optimization settings
    call_to_action_type: New call to action button type — NOTE: Meta API may reject this on existing creatives
    lead_gen_form_id: Lead generation form ID for lead generation campaigns
    ad_formats: List of ad format strings for asset_feed_spec (e.g., ["AUTOMATIC_FORMAT"] for
               Flexible ads, ["SINGLE_IMAGE"] for single image)
    creative_features_spec: Dict of Advantage+ Creative feature opt-ins/opt-outs.
               Each key is a feature name, value is {"enroll_status": "OPT_IN"|"OPT_OUT"}.
               Sent as a top-level field (not inside degrees_of_freedom_spec).

Returns:
    JSON response with updated creative details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
messageNo
headlineNo
messagesNo
headlinesNo
ad_formatsNo
creative_idYes
descriptionNo
access_tokenNo
descriptionsNo
lead_gen_form_idNo
optimization_typeNo
call_to_action_typeNo
dynamic_creative_specNo
creative_features_specNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the transparency burden. It discloses the Meta API limitation that content fields are not updatable and lists which parameters may be rejected. It could be more precise about actual rejection behavior but otherwise gives strong context for a mutation tool.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and the critical limitation, then follows with a structured Args list. It is somewhat long, but the length is justified by 15 parameters and the need to warn about API restrictions.

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 tool with 15 parameters, no annotations, and low schema coverage, the description covers the purpose, limitations, parameter semantics, and alternative workflow. The presence of an output schema means return values do not need further description. This is comprehensive for the tool's complexity.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description details all 15 parameters with usage notes, including that name is 'most reliable', which fields 'may be rejected', and how to use optimization_type, ad_formats, and creative_features_spec. This significantly compensates for the empty schema descriptions.

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?

Description clearly states 'Update an existing ad creative's name or optimization settings', specifying the exact action and scope. It distinguishes itself from sibling tools like create_ad_creative and update_ad by explicitly noting content changes require creating a new creative and updating the ad to reference it.

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?

Provides explicit when-to-use guidance: updating name or optimization settings only. It also states when NOT to use it (content updates) and names the alternative workflow: 'create a new creative ... and update the ad to reference the new creative via update_ad'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pralayasimha23/meta-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server