Skip to main content
Glama

meta_ads_creatives_create_dynamic

Creates a Dynamic Creative for Meta Ads, automatically generating and optimizing combinations from multiple images, headlines, and body texts. Returns the new creative ID.

Instructions

Creates a Dynamic Creative — Meta auto-generates and optimises combinations from multiple images, headlines, bodies, and CTAs. Returns the new creative id. Mutating, reversible via rollback_apply. Use when you want Meta to learn the best-performing asset mix rather than testing manually. For static single-image ads use meta_ads_creatives_create; for explicitly-controlled multi-card layouts use meta_ads_creatives_create_carousel. Supply 2–10 images, 1–5 of each text field; Meta combines them at serve time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
nameYesCreative name shown in Ads Manager.
page_idYesFacebook Page ID that the ad will be published as. Must be a page the authenticated user has permission to post from. Required by Meta for every creative — ads cannot run without a page identity.
image_hashesYesImage hashes to include in the rotation. 2–10 recommended for meaningful optimization; Meta accepts up to 10. Upload via meta_ads_creatives_upload_image / meta_ads_images_upload_file first.
bodiesYesPrimary body text variants. 1–5 accepted. Meta recommends ≤125 characters per body.
titlesYesHeadline variants. 1–5 accepted. ~40 characters fits most placements.
link_urlYesDestination URL shared across all combinations. Must be HTTPS and domain-verified.
descriptionsNoOptional link-caption variants (0–5). Not all placements render these.
call_to_actionsNoOptional CTA variants (0–5). Values drawn from the same set as meta_ads_creatives_create (LEARN_MORE / SIGN_UP / SHOP_NOW / etc.).
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It notes mutability and reversibility via rollback_apply, and mentions return value. However, it lacks details on permissions, rate limits, error conditions, or what happens if requirements are not met.

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 concise and well-structured: first sentence explains what it does, then behavior, return, usage guidance, alternatives, and parameter details. Every sentence adds value without redundancy.

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 9 parameters and no output schema, the description covers the creative's nature, usage context, parameter constraints, and alternatives. It lacks some details on error handling and exact return format, but overall is fairly complete.

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%, baseline 3. The description adds value beyond schema by recommending quantities (2-10 images, 1-5 text), character limits, and prerequisites (upload images first). It also clarifies optional parameters and their rendering behavior.

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 the tool creates dynamic creatives, explaining that Meta auto-generates and optimizes combinations. It distinguishes from siblings by naming alternatives (meta_ads_creatives_create, meta_ads_creatives_create_carousel) and specifying their use cases.

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 states when to use: 'Use when you want Meta to learn the best-performing asset mix rather than testing manually.' Also provides clear alternatives and specific input quantity guidance (2-10 images, 1-5 text fields).

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/logly/mureo'

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