Skip to main content
Glama

update_ad_creative

Update an existing ad creative's name or optimization settings. Content fields cannot be changed; to update content, create a new creative.

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
creative_idYes
access_tokenNo
nameNo
messageNo
messagesNo
headlineNo
headlinesNo
descriptionNo
descriptionsNo
optimization_typeNo
dynamic_creative_specNo
call_to_action_typeNo
lead_gen_form_idNo
ad_formatsNo
creative_features_specNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses API limitations and parameter behavior. Explains that content fields may be rejected, and only name and certain optimization settings are reliably updatable. Documents the structure of creative_features_spec and ad_formats.

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 fairly long but well-structured with an important notice at the top and a clear parameter list. It is front-loaded with key limitations. Some redundancy (multiple 'NOTE' lines) could be trimmed, but overall it balances detail and readability.

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?

Given the complexity (15 parameters, no annotations), the description covers essential behavior and parameter semantics. The output schema exists, so return values are already documented. Lacks examples of usage or error handling, but is complete enough for most use cases.

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 description coverage is 0%, so the description must explain parameters. It lists all 15 parameters with brief notes, including important caveats for content fields. However, it could provide more detail on the exact format of dynamic_creative_spec or lead_gen_form_id.

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 clearly states 'Update an existing ad creative's name or optimization settings,' which is a specific verb+resource combination. It distinguishes from siblings like 'create_ad_creative' (creation) and 'update_ad' (ad-level update) by focusing on 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 Guidelines5/5

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

Explicitly warns about Meta API limitations: content fields (message, headline, etc.) cannot be updated, only name and optimization settings. Provides an alternative (create new creative and update ad reference). Includes guidance on optimization_type and ad_formats parameters.

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/pipeboard-co/meta-ads-mcp'

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